Automation — WHEN, IF, THEN
A rule reads as a sentence: WHEN something happens, IF some things are true, THEN do these things.
That is the whole model. There is no flowchart to draw and no scripting.
Before you start
- You need the
tenant.automation.managepermission. - Set up pipelines, lead statuses, tags and your team first — a rule can only point at things that exist.
Steps
- Go to Settings → Automation.
- New automation, name it something you will recognise in six months.
- WHEN — choose one trigger.
- IF — add conditions, or none. Choose whether all or any must match.
- THEN — add steps in the order they should run.
- Review, then activate. A rule stays a draft until you do.
WHEN — the ten triggers
| Trigger | Fires when |
|---|---|
| Lead created | A lead arrives, however it arrived |
| Lead assigned | A lead gets an owner, or a new one |
| Lead status changed | |
| Lead stage changed | |
| Deal created | |
| Deal stage changed | |
| Deal won | |
| Deal lost | |
| A call is logged on a lead | |
| A follow-up on a lead falls due |
IF — the conditions
A condition is a field, a comparison and a value. Seven comparisons:
is · is not · contains · greater than · less than ·
is set · is not set
Your own custom fields appear in the field list alongside the built-in ones.
There is no nesting — one all or any choice for the whole rule. If you need more than that, the right answer is a second rule.
THEN — the actions
| Action | |
|---|---|
| Assign the lead to someone | |
| Change the lead's status | |
| Move the lead to a stage | |
| Add a tag / Remove a tag | |
| Create a follow-up | With a title, type, due in N days, and who it is for |
| Notify someone | |
| Assign the deal to someone | |
| Move the deal to a stage | |
| Notify about the deal |
Actions reuse the ordinary rules. Moving a lead to a stage goes through the same path a person uses, so forbidden transitions and required lost reasons still apply. An automation cannot do something a person could not.
Three rules worth building
Nobody picks up new enquiries after 6pm WHEN a lead is created · IF owner is not set · THEN assign to the duty caller, and create a follow-up due in 1 day.
A deal went quiet WHEN a follow-up falls due · IF stage is Negotiation · THEN notify the manager.
Lost deals get tagged for a win-back campaign later WHEN a deal is lost · THEN add the tag "Win-back".
What this affects elsewhere
- Everything an automation does appears on the record's timeline, so a person reading a lead can see what was done by a rule and what by a human.
- Each rule has an execution history with the reason for every failure.
What you cannot change later
Nothing is permanent, but two behaviours are deliberate and surprise people:
The same transition twice runs the rule once. A lead pushed to Qualified, back, and to Qualified again gets one follow-up, not two. The alternative acts on a customer twice because somebody fixed a mis-click.
A rule that fails does not fail the work that triggered it. A broken automation can never stop a lead being imported. The run is recorded as failed, with a sentence saying why.
There are also hard ceilings — a rule will not run away: a per-record daily limit, a cooldown, and a depth limit that stops one rule triggering another endlessly.
What is not built
Send a WhatsApp template is available as a step on leads and deals. It
sends an approved template — the one WhatsApp message allowed at any time — to
the customer. Each blank can use {first_name}, {name}, {city},
{owner_name} or {business}, with a fallback after a bar:
{first_name|there}. A customer who opted out is not messaged.
Not available yet. Email as an automation action (no email provider is connected), and free-text WhatsApp messages — those are only allowed inside the 24-hour window, so a rule firing hours later would be refused.
Not available yet. Time-based triggers — nothing fires "three days after X". Webhooks as an action. Creating a deal from a lead automatically.
Not available yet. Triggers on contacts. Nothing in the CRM creates a contact directly, so the trigger could never fire.
If it does not work
| What you see | What it means | What to do |
|---|---|---|
| The rule never runs | It is still a draft | Activate it |
| It ran once and not again | Same transition, same record — by design | Expected |
| "Skipped" in the history | Conditions did not match | Not a failure |
| "Failed" with a sentence | Read it — usually a person who left, or a stage that was archived | Fix what it points at |
| Nothing happens at all | The queue worker is not running | Ask your administrator |