Automations
Build workflows that connect triggers, your apps and your calls.
Automations run work for you without anyone clicking: when a form is submitted, a call completes or a message arrives, a workflow can update a sheet, send an email, post to Slack and more. You build them on a visual canvas. Only owners and admins can use Automations.
The Automations area
| Tab | What it shows |
|---|---|
| Workflows | All your workflows. Filter by All, Active, Draft or Archived, and search by name. |
| Executions | The run history: every run with its status, duration and details. |
| Templates | Ready-made workflows you can start from. |
| Settings | Workspace defaults for automations, such as the time zone and failed-run notifications. |
Build a workflow
- 1
Create it
Choose Create workflow and give it a name.
- 2
Add a trigger
Choose Add node and start with a trigger. The node picker goes from category to app to operation.
- 3
Add steps
Add the actions that should run after the trigger and connect them. Apps need a connection from Integrations.
- 4
Fill in each step
Open a node to set its fields. A field can hold fixed text or an expression that uses data from earlier steps.
- 5
Test
Choose Execute workflow to run a safe test with sample data.
- 6
Publish and activate
Choose Publish, then turn on Activate workflow. A workflow only runs from its trigger once it is published and active.
Triggers
- Webhook: starts when another system sends a signed request.
- Manual: starts when you choose Run now.
- Schedule: starts on a schedule.
- Form submission: starts when someone submits a public form, which has its own share link.
- Gmail message received, Outlook message, Slack event and WhatsApp message received.
- Call completed: starts when one of your agents finishes a call.
Steps you can add
- Flow control: Filter, If/Else, Switch, Wait and Form Ending.
- Core: Edit Fields and Split Out.
- Actions for apps such as HTTP Request, Email, Slack, WhatsApp, HubSpot, Google Sheets, Gmail, Drive and Calendar, Cal.com, Calendly, Microsoft (Outlook, Excel, Dynamics), Zoho, Salesforce and GoHighLevel.
- AI steps and calls through your voice agents.
Use data from earlier steps
Anywhere a field accepts an expression, write it inside double curly braces. Plain text and expressions mix freely, for example Hi {{ $json.name }}.
| Write | Meaning |
|---|---|
$json.name | A field of the item the previous step handed on |
$('Step name').item.json.email | A field from an earlier step, for this same item |
$('Step name').first().json.email | A field from that step's first item |
$now, $today | The current date and time |
Expressions are checked in a safe sandbox: they can only read the data of the run, and they time out if they take too long. A live preview shows the result as you type.
Test versus run
- Execute workflow is a safe test: nothing is sent to other services, and calls to outside systems are simulated. A dialog lets you fill in test inputs or leave them blank to use a sample answer.
- Run now is a live run. It only appears when the workflow is active and has a manual trigger.
- After you edit an active workflow, choose Activate new version to make the changes live.
Run history
The Executions tab (also called Run history) lists runs with their start time, workflow, type (live or test), duration and status. Open a run to see its calls and each step. Filters narrow it by workflow, live or test, and status.
| Status | Meaning |
|---|---|
| Queued, Starting, Running | On its way or in progress |
| Retrying | A step failed and will try again |
| Waiting for response | Paused until a person or system answers |
| Succeeded | Finished without problems |
| Failed | Stopped with an error |
| Not confirmed | The result could not be confirmed |
| Cancelled, Skipped | Stopped or not needed |
Templates
The Templates tab has ready-made workflows for common jobs, such as appointment confirmation, candidate screening, customer feedback, inbound triage, payment reminders, post-call follow-up and speed to lead. Search them or filter by app, then use one to start your own copy.
Tips and limits
- Archived workflows are read-only until you restore them.
- If a teammate saves the same workflow, you will see Update conflict. Choose Reload workflow to get their version.
- The editor saves as you go and shows Saving…, Saved or Save failed. Retry at the top.
- How long run history is kept depends on your plan.