Integrations
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.
Triggers and actions
In the Duaer node panel, a trigger is the step that starts a digital organization, such as a schedule, a webhook, or an app event. An action is a step that runs after the digital organization has already started, such as reading a sheet or sending a message.
Built-in integrations do not need a community package. Most apps also have a credential page that explains how to store a key or OAuth in Duaer.
When the app node cannot call the API you need
Use custom operations: HTTP Request reuses that app’s authentication. Community nodes have separate risk and troubleshooting notes.
Questions
How do triggers differ from actions in Duaer?
In Duaer, a trigger starts a digital organization. An action runs a step after it has started. Schedules, webhooks, and app events are triggers. Writing a sheet row or sending a message is an action.
Do Duaer built-in integrations need a community package?
No. Built-in integrations ship with the instance. Community nodes are extra packages and have their own risk notes.
In this section
Risks 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.