Integrations
Integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
Where to go next
- Built-in integrations: triggers and actions that ship with the instance.
- Built-in credentials hub: per-service credential fields.
- Custom operations: HTTP Request when the app node lacks an operation.
- Community node risks: read before installing a community package.
Related to Create and edit credentials
How to create and save a credential on the instance is under Create and edit credentials. This section focuses on per-service fields.
Questions
How do built-in integrations differ from community nodes in Duaer?
Built-in integrations ship with the instance. Community nodes are extra packages — read the risk notes before you install them.
What if Duaer has no node for the API I need?
Check built-in nodes first. If the operation is missing, use custom operations: HTTP Request can reuse that app’s saved authentication.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a digital organization. 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.
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.