Choose a workflow node
On this page
Each node performs one operation. Start with the smallest set needed for your workflow, then connect the execution paths and name the results that later steps will use.
Core nodes#
| Node | Use it for | Result or next step |
|---|---|---|
| Function | Python validation, transformation, calculations | Named output, then next node |
| HTTP Request | Calling an upstream API | Named response, then next node |
| Condition | A true/false test | True or false branch |
| Decision | Ordered routing rules | First matching connected branch |
| Database | SQL queries and mutations | Query result, then next node |
| Schedule | Creating a job from runtime data | A scheduled execution, not an inline call |
| Selector | Saving a shared value in a refresh workflow | Stored selector update |
| WebSocket | Publishing an event to a channel | A message sent to listeners |
| IdP Authorize / IdP Users | User authorization and identity operations | Authorized identity or user result |
The library also includes specialized integrations such as notifications, wallet payments, and service connectors. See integration nodes before adding an operation with external effects.
Add and connect a node#
Open the node library from the canvas or a connection's add control. Configure the selected node, give it a unique descriptive name, and connect it to the intended predecessor and successor.
Confirm the action's entry node. For a branch, connect the actual branch output rather than only arranging the node visually.
Understand outputs#
A successful named result becomes available as ${NodeName} to later nodes in the same run. In Python, use it directly, for example customer = ${FetchCustomer}. An unquoted JSON selector resolves to its parsed value; quote the selector when you need text.
Test the complete path after adding a node. A standalone node test can help inspect one operation, but it cannot prove that earlier authentication, data production, and routing all work together.
Need to investigate a problem? Start with troubleshooting