Integrations
Use Cockpit in Duaer
In Duaer, the Cockpit node works with Cockpit from a workflow. It offers 5 operations on Collection, Form, and Singleton.
Add Cockpit to a Duaer workflow
- On the Duaer canvas, open the node panel, search for Cockpit, and connect it after the previous node.
- In Credential to connect with, pick or create a Cockpit API credential. Refer to Cockpit credentials.
- Pick a Resource and an Operation. For example, to create a collection entry, pick Collection and Create an Entry.
- Fill the fields that operation shows, such as Collection Name or ID and JSON Data Fields.
- Select Execute step and check the output.
Cockpit operations in Duaer
The Cockpit node in Duaer offers these operations, grouped by resource:
- Collection › Create an Entry: Create a collection entry.
- Collection › Get Many Entries: Get many collection entries.
- Collection › Update an Entry: Update a collection entry.
- Form › Submit a Form: Store data from a form submission.
- Singleton › Get: Get a singleton.
Use Cockpit as a tool for an AI Agent in Duaer
In the Tool input of an AI Agent, search for Cockpit and add it. The agent decides when to call it. For a field the model should fill, select the sparkle next to it or write $fromAI('name', 'what to put here'); fixed values stay as you set them.
Call a Cockpit endpoint the node does not cover
Add an HTTP Request node, set Authentication to Predefined Credential Type, pick Cockpit API as the credential type, and select the same credential. Duaer signs the request with it, so you only fill in the method and URL. Refer to custom operations.
Questions
Which Cockpit operations does Duaer support?
Duaer's Cockpit node offers 5 operations on Collection, Form, and Singleton. For example, Collection has Create an Entry, Get Many Entries, and Update an Entry.
Which credential does Cockpit use in Duaer?
Duaer's Cockpit uses a Cockpit API credential. The secret stays in the credential, not in node parameters.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.