Automations
Triggers
A trigger is the event that starts an automation. Pick one when you create the automation; most triggers can be narrowed further with a small config.
| Trigger | Fires when | Narrow it by |
|---|---|---|
Lead created | A new lead enters the project. | – |
Stage entered | A lead moves into a stage. | A specific stage, or any stage of a category (open/won/lost). |
Stage exited | A lead leaves a stage. | A specific stage or category. |
Tag added | A tag is added to a lead. | A specific tag (blank = any). |
Tag removed | A tag is removed. | A specific tag. |
Form submitted | A lead-capture form is submitted. | – |
Ad lead received | A lead arrives from Google / Meta ads. | – |
Message received | An inbound WhatsApp / SMS / email / DM arrives. | A specific channel. |
No reply for… | A lead has had no activity for N hours. | The number of hours. |
Targeting stages generically
For stage triggers you can either pick one exact stage, or match a whole category, for example “entered any won stage”. Matching by category means one automation works across every pipeline without you wiring up each stage by hand.
The “no reply for N hours” trigger
This one is time-based: a background job checks every few minutes for open leads that have gone quiet for at least the number of hours you set, and fires once per silent period. A new message from the contact resets the clock, so the follow-up re-arms for the next lull.
Requires the scheduler
The no-reply trigger needs the automations cron configured. If your no-reply rules never fire, confirm the scheduler is set up (see your operator / the setup notes).