Organizations and data
Extend nodes in Duaer
Most work uses built-in nodes. Prefer custom operations first; build a custom node or install a community package only when you will reuse the step.
Preferred order
- Search built-in triggers and actions in the node panel.
- When an app node lacks an API: use custom operations (HTTP Request + saved auth).
- If you still need a reusable step: evaluate a community node (read risks first) or develop a custom node the way your instance supports.
Related to canvas nodes
How nodes connect and pass data is under Work with nodes. This page only answers where to extend when built-ins are not enough.
Questions
Do most Duaer users need to create nodes?
Usually no. Prefer built-in nodes and custom operations. Build a custom node or install a community package only when built-ins are not enough and you will reuse the step.
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.
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.
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.
CanvasWork with nodes in Duaer
In Duaer, a node is an entry point for retrieving data, a function to process data, or an exit for sending data.