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 saved automation, with status (enabled / disabled) and a short summary.
• Preview pane (right) — the steps of the selected automation.
• Editor screen — the new and edit routes (/automations/new and /automations/[id]) open a full-page editor for the trigger plus steps.

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 in the editor.
3. Enable or disable without leaving the list.
4. Test — most automations support a dry-run against a sample record before you flip them on.

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.
• Always test before flipping a new automation on. Especially for anything customer-visible.

Related

• Workflows
• Goals overview