Built-in nodes
Built-in nodes are the ones every deployment has. They need no connection to an outside system and no integration to be enabled, so they are available in the picker from the moment you open the editor. Nodes that belong to a connected system—a CMS, a chat workspace, an issue tracker—live under Integrations instead.
This section is the field-by-field catalog. For how each kind of node fits into a flow, read the concept pages: Triggers, Actions, Conditions and branching, and Loops and iteration.
Triggers
How a run starts. See Triggers.
| Node | What it does |
|---|---|
| Schedule | Starts a run on a recurring schedule, or when you start one by hand. |
| Webhook | Starts a run when an external system posts to a URL that belongs to the trigger. |
| On Demand | Starts a run when you run it yourself, or when another automation calls it. |
| Automation Completed | Starts a run when a chosen automation finishes. |
Actions
The steps that do work. See Actions.
| Node | What it does |
|---|---|
| HTTP Request | Sends an HTTP request to any URL and captures the response. |
| Script | Runs a script in a sandbox and returns its result as the step's output. |
| AI Agent | Runs an AI agent on a prompt, with tools, and optionally pauses for a person. |
| Automation | Runs another automation through its on-demand trigger. |
| Sleep | Pauses the flow for a set duration, then continues. |
| Log | Writes a line to the run's execution log and continues unchanged. |
| Stop with Error | Deliberately fails the run when the flow reaches it. |
Conditions
Routing the flow down one of two paths. See Conditions.
| Node | What it does |
|---|---|
| Expression | Routes on a boolean expression you build from comparisons. |
| Script | Routes on whether a script returns a truthy value. |
| AI Judgment | Routes on an AI agent's answer to a yes/no question. |
| Random (A/B Split) | Routes a percentage of runs one way and the rest the other. |
Flow control
| Node | What it does |
|---|---|
| Loop and Loop End | A matched pair that brackets a section of the flow and runs it once per item in a list. They are added together and configured as one thing, so they are covered in Loops and iteration rather than as separate entries here. |
Connections
| Connection | What it connects to |
|---|---|
| Custom OAuth | Any OAuth 2.0 service, for the HTTP Request and OpenAPI actions to authenticate against. |
Every other connection type belongs to a particular integration—see Integrations and Connections.
What every node has
Beyond its own fields, every node carries the same three tabs:
- Input—values you map in from earlier steps, before the node runs.
- Output—values you map out of the node's result.
- Display—an optional Title, appended to the node's type name on the canvas, and an optional Description, shown as the first subtitle line on its card.
Every action additionally carries Test Output on its Advanced tab: JSON returned as the step's output when a dry run suppresses its real work, so later steps still see a realistic shape. Leave it blank to output nothing.