Actions

Actions are the steps your workflow performs after a trigger fires. They're the "do this" part of your automation: send a Slack message, call an API, update a database, classify text with AI, or any of 130+ other operations.

Action categories

How actions work

1. A trigger fires and produces output data (e.g., a webhook payload with { email, name, message })
2. The first action receives that data and can reference any field using variables: {{trigger.body.email}}
3. The action executes: it does something (sends a message, calls an API, inserts a row)
4. The action produces output, which becomes available to the next node as new variables
5. This chain continues until the workflow ends or an End node stops it

Every node in the chain can reference output from ANY previous node, not just the immediately preceding one.

The 3-tab pattern

Most action nodes have 3 configuration tabs:

Adding an action to your workflow

1. Click + Add node in the bottom bar (or after completing the previous node's setup)
2. Browse by category tabs (Flow Control, Integrations, AI, etc.) or type in the search bar
3. Click the node to add it; the Initialise tab opens immediately
4. Choose a template or start from scratch → Continue
5. Fill in the Configure tab fields
6. Run the Test (required for most nodes)
7. Click Save to commit the node to the canvas

Connections

Most integration actions require a connection: an authorized account for the app you're connecting to. For example:

• Slack actions need a Slack workspace connection
• Gmail actions need a Google account connection
• Stripe actions need a Stripe API key

Set up connections in Build → App Authorizations before using integration nodes. Once connected, the same connection is available to all workflows in your workspace.

Credits

Some actions consume credits:

Monitor usage in Monitor → Credit Usage.