Automations
Automations run workflows: a trigger followed by a chain of actions. They replace scripts and cron jobs for everyday work, such as notifying a team when a deal is won or syncing new rows to another service.
Concepts
| Concept | Description |
|---|---|
| Workflow | A named chain of nodes. It is either in test mode, published (live) or paused. |
| Trigger | What starts the workflow: rows created / updated / deleted in a table, a schedule (every N minutes, hourly, daily, weekly, monthly), or an incoming HTTP request (webhook). |
| Action node | A step: create / update / delete a row, list or get rows, send an email (SMTP), send an HTTP request, send a Slack message, generate text with AI. |
| Router | Splits the workflow into branches with conditions. |
| Iterator | Runs the following nodes once for every item of a list. |
Build a workflow
- Sidebar → + New → Automation and name it.
- Choose a trigger, e.g. Rows are created in the
Leadstable. - Click + below the trigger and add an action, e.g. Send an email.
- Fill the action using formulas that reference earlier nodes, for example
the subject
New lead:followed by the lead’s name from the trigger. - Click Test run. The trigger waits for a real event (or uses sample data) and shows the output of every node.
- Click Publish to make the workflow live.
Referencing data
Each node’s output can be used in the following nodes. In a formula input, open the data explorer and choose a node, then a value. Values from a list become available per item after an Iterator.
History and debugging
The History panel lists every run with its status, duration and the input and output of each node, which makes failed runs easy to inspect. Fix the workflow, then publish again.
Integrations
Actions that talk to external services use an integration stored in the automation (SMTP credentials, a Slack bot token, an AI provider). Integrations are shared by all workflows of the automation and never shown to agents in clear text.
With an agent
Agents can create workflows and nodes through MCP and publish them with
publish_workflow. Keep the project in Assisted mode if you want to approve
each change first (Autonomy & approvals).