Automation and workflows

Add an AI step to a workflow

Drop a real Claude-powered step into a flow — summarize a record, draft an email, classify an input, or suggest a next best action — and feed its output into the steps that follow.

Build your first workflow

Pick a trigger, add a condition, drop in an action, dry-run it, and turn on a live, no-code workflow — the full path from a blank flow to automation that runs on its own.

Read run history and retry

Open any run to see a per-node trace, find the step that failed and why, retry from the failed step, and rely on idempotency keys, loop guards, and an on-failure recovery branch.

Triggers, conditions and branches

How a workflow knows when to run and where to go: the events that trigger it, the AND/OR conditions that filter it, and the branches that route a run down the right path.

Dry-run a workflow before turning it on

See what a workflow would do without it doing anything. The dry run is the cheapest way to find out that your condition matches four thousand records instead of four.

Send an email from a workflow

Automated email that still reads as if a person sent it — choosing the template, getting merge tokens right, and the checks worth doing before you turn it on.

The workflow actions, explained

What a workflow can actually do once a trigger fires — update records, create work, send email, call your own systems, and add an AI step you can branch on.

The workflow templates gallery

Prebuilt automations you install as a draft in one click, then adapt. Faster than a blank flow, and a good way to see how the pieces fit together.

Why my workflow did not run

The handful of reasons an automation stays quiet — inactive, a trigger that never fired, a condition that excluded everything, or an action that failed — and how to tell which.