Automations
An automation is a simple rule that says: when this happens to a lead, do this one thing. For example, "when a new lead arrives, create a task to call them within 1 hour", or "when a lead has had no activity for 14 days, move it to a Nurture stage". You must be a site administrator to manage automations.
Open it from Manage Site > Automations in the site menu.
Automations Table
| Column | Description |
|---|---|
| Name | The rule's name. |
| Trigger | What starts the rule: New lead, Stage change, No activity for N days, or Task overdue. |
| Action | What the rule does: Create task, Enroll in campaign, Change stage, or Assign to user or team (a team assignment rotates through the team's members in round robin order). |
| Active | Yes when the rule is running. Rules are off until you mark them active. |
| Actions | Edit and Delete. Deleting a rule keeps its run history. |
Click Add Automation to create a rule. The fields are described in Trigger and Action Reference.
Recent Runs
Below the table, Recent runs lists the 25 most recent times a rule ran, with the time, the automation, a link to the lead, and the result. The result begins with a status:
| Status | Meaning |
|---|---|
done | The action was carried out, for example "task created" or "moved to Contacted". |
skipped | The rule ran but did nothing, with the reason, for example "skipped: already in stage" or "skipped: no user to assign the task to". |
failed | An error occurred. The message shows what went wrong. |
Use this list to check that a new rule behaves the way you expect.
How Rules Run
- One rule, one trigger, one action. To do two things when a lead arrives, create two automations.
- At most once per event. A rule runs only once for the same lead and the same trigger event. If a trigger is detected twice, the action is not repeated.
- Event triggers run immediately. "New lead" runs when a lead is received or created, and "Stage change" runs when someone changes a lead's stage in the portal.
- Time-based triggers run hourly. "No activity for N days" and "Task overdue" are checked by a background job once an hour, and each check handles at most 200 leads per rule.
- Automations never start other automations. If one rule moves a lead to a new stage, that does not trigger a "Stage change" rule, so rules cannot loop.
- Rules are checked for the whole site. There is no way to limit a rule to one agent or team, except by the filters each trigger offers.
Important Cautions
- Turning on a time-based rule can affect leads you already have. A "No activity for N days" rule looks at every open lead on the site, not only new ones. The first hourly check after you activate it will run the action for all existing leads that match, up to 200 leads per hour. A "Task overdue" rule does the same for tasks that are already overdue. Check the number of matching leads first (for example with a smart list), and start with the rule inactive while you review it.
- Stage-change rules react to portal edits only. They run when a person changes the lead's stage on the lead form. Stage changes made some other way do not trigger them.
- New-lead rules run for leads received through the site and for leads you add by hand in the portal. They do not run for existing leads.
- The "Enroll in campaign" action follows the normal enrollment rules: the lead needs an email address, must be opted in and must not be unsubscribed. Otherwise the run is shown as skipped.