Automations

How automations work

An automation is a simple rule: when something happens (a trigger), if the lead matches (conditions), do a list of things (actions). No code required.

Build one

1. 1
   New automation

   Go to Automations → Rules and pick a trigger (or start from a recipe).
2. 2
   Add conditions

   Optionally narrow it to certain leads.
3. 3
   Add actions

   Choose what should happen, in order.
4. 4
   Turn it on

   Toggle Active. It starts running on the next matching event.

Pipeline scope

An automation can apply to all pipelines or be scoped to one. A pipeline-scoped automation only runs for leads in that pipeline.

When automations run

Most triggers fire immediately, in the same moment the event happens, a stage move, a new lead, an inbound message. The one exception is “no reply for N hours”, which is time-based and is checked on a schedule every few minutes.

Order and “stop after match”

If several automations share a trigger, they run in their listed order. Turn on Stop after this matches on an automation to skip the lower-priority ones once it fires, useful for “first match wins” setups.

No loops

Actions that change a lead (move stage, add tag) do not re-trigger other automations. Every event is capped at a single hop, so you can never build an accidental loop.

Kill switch

You can pause all automations for a project from Settings → CRM. There is also a platform-wide switch for operators. Individual automations have their own Active toggle.