Node Types
Nodes are the building blocks of a blueprint. Each node performs one specific action, and you connect them together to create your automation.
Node categories
The node palette in the workflow builder organizes nodes into four groups:
Triggers
Triggers define how a blueprint starts. Every blueprint needs exactly one trigger.
| Node | What it does |
|---|---|
| REST API Trigger | Starts the workflow when an external system sends an HTTP request |
| Attribute Change Trigger | Starts the workflow when a contact's attribute changes |
For details on how triggers work and how to configure conditions, see Triggers.
Flow Control
Flow control nodes let you add logic and structure to your automation.
| Node | What it does |
|---|---|
| Condition | Takes a different path based on a true/false check |
| Loop | Repeats a set of steps for each item in a list |
| Wait | Pauses the workflow for a specified duration |
Actions
Action nodes perform core operations within your workflow.
| Node | What it does |
|---|---|
| HTTP Request | Makes an HTTP call to an external API |
| Log | Records a message in the execution report for debugging |
| Set Variable | Stores a value for use by downstream nodes |
Integrations
Integration nodes connect to external services and providers.
| Node | What it does |
|---|---|
| Send Email | Sends an email using a configured provider (e.g., SendGrid) |
| Send SMS | Sends an SMS using a configured provider (e.g., Twilio) |
| Database | Reads from or writes to an external database |
Integration nodes typically require a credential to authenticate with the external service. See Node Configuration for details.
Use the search bar in the node palette to find nodes quickly. Type keywords like "HTTP", "email", "condition", or a provider name like "Twilio".
How nodes connect
Nodes connect through lines on the canvas. The connections define:
- Execution order -- which node runs after which
- Data flow -- output from one node is available as input to the next
Each node receives the output of its upstream nodes and can reference that data through expressions.
Choosing the right node
| You want to... | Use this |
|---|---|
| Start a workflow from an external system | REST API Trigger |
| React to a data change | Attribute Change Trigger |
| Make a decision based on data | Condition |
| Call an external API | HTTP Request |
| Send a message to a user | Send Email / Send SMS |
| Process a list of items | Loop |
| Debug your workflow | Log |
| Wait before the next step | Wait |
Next steps
- Node Configuration -- how to set up each node
- Triggers -- deep dive into trigger types
- Blueprints -- how nodes fit into the bigger picture