Automations

An automation is a multi-step sequence that runs in response to record events — a lead is created, an opportunity moves stages, a job is completed. Automations are deterministic: same trigger plus same inputs always produce the same actions.

Layout

• Template cards (left) — each automation available to your organization, showing its trigger, step count, and an on/off switch. Templates marked System ship with the product. Click a card to select it.
• Automation Preview (right, top) — the selected automation's description, its Active or Paused badge, step count, and the trigger and entity it fires on.
• Run Preview (right, bottom) — the ordered sequence of steps that runs when the trigger fires.
• Editor screen — /settings/automations/new and /settings/automations/[id] open a full-page editor for the trigger plus steps. Refresh in the page header reloads the list.

Common tasks

1. Create an automation — pick a trigger, then string together actions (send email, create task, update field, branch on condition).
2. Edit an existing automation — use Edit on the card, or open the editor route directly.
3. Enable or disable with the switch on the card, without leaving the list.
4. Check the steps before enabling — select the card and read Run Preview. There is no dry-run against a sample record, so the step list is what you have to reason from.

Automations vs goals

• Use an automation for deterministic if-then logic ("when this happens, do that").
• Use a goal for AI-driven evaluation with confidence scores ("when records look like this, propose doing that").

Tips

• Keep each automation focused on one thing. A 20-step automation is a debugging nightmare.
• Read Run Preview end to end before enabling anything customer-visible. Once the switch is on, the next matching record fires it for real.

Related

• Workflows
• Goals overview