Trigger and Action Reference
This page describes every field on the Add/Edit Automation form, which you open with Add Automation on the Automations page. You must be a site administrator.
The form has one When (trigger) and one Then (action). Only fill in the fields for the trigger and the action you picked; the others are ignored.
General Fields
| Field | Description |
|---|---|
| Name | A name for the rule, up to 150 characters. Required. It is also used as the default task title for "Create task". |
| When | The trigger. See below. |
| Then | The action. See below. |
| Active | Yes or No. New rules default to No. |
Triggers
New lead
Runs when a new lead is received through the site or added by hand in the portal.
| Field | Description |
|---|---|
| New lead trigger: only for lead type | All lead types, or one lead type. When a type is chosen, leads of other types are ignored. |
Stage change
Runs when a person changes a lead's stage in the portal lead form.
| Field | Description |
|---|---|
| Stage change trigger: moved to stage | Any stage, or one pipeline stage. The rule runs only when the lead is moved into that stage. |
Moves made by another automation's "Change stage" action do not trigger this.
No activity for N days
Checked once an hour. Runs for leads that have had no activity for the number of days you enter.
| Field | Description |
|---|---|
| Inactivity trigger: days with no activity | A whole number from 1 to 3650. Required. |
| Inactivity trigger: only leads in stage | Any stage, or one pipeline stage. This uses the same field as the stage change trigger. |
How "no activity" is decided:
- Only leads whose status is not Closed or Spam are considered.
- A lead's last activity is the most recent entry on its timeline that shows someone worked it: notes, calls, appointments, stage changes and similar. Entries the system creates on its own do not count: tasks and campaign enrollments created automatically, campaign emails sent, and email opens and clicks. If a lead has no such entry, its received date is used.
- A rule runs once for each "last activity" time. If the lead gets new activity and then goes quiet again, the rule can run again.
Task overdue
Checked once an hour. Runs for open tasks linked to a lead that are past due.
| Field | Description |
|---|---|
| Task overdue trigger: hours past due | Hours after the due time before the rule runs. 0 means as soon as the task is overdue. |
Only open tasks that have a due date and are linked to a lead are considered. The rule runs once for each task.
Actions
Create task
Adds a task to the lead.
| Field | Description |
|---|---|
| Create task: task title | The title of the task. Required, up to 200 characters. |
| Create task: due in hours | How many hours from now the task is due. Defaults to 24. 0 makes it due immediately. |
| Create task / Assign: user | Who the task is assigned to. The default option is the lead's assigned user, and if the lead has none, the site's default lead user. |
If nobody can be found to assign the task to, the run is skipped. The task's details say "Created by automation" with the rule's name, and a "Task added by automation" entry is added to the lead's timeline.
Enroll in campaign
Enrolls the lead in a drip campaign.
| Field | Description |
|---|---|
| Enroll in campaign | The campaign. Required. It does not need to be a campaign for the lead's type. |
The lead must have an email address, be opted in, and not be unsubscribed, and must not already be in that campaign; otherwise the run is skipped. The campaign must have at least one step. The enrollment is accepted even if the campaign is currently inactive, but no emails are sent while it stays inactive.
Change stage
Moves the lead to a pipeline stage.
| Field | Description |
|---|---|
| Change stage: move to | The stage. Required. |
The lead's basic status is updated to match the stage, and the change is saved in the lead's stage history. If the lead is already in that stage, the run is skipped.
Assign to user or team
Assigns the lead to a person.
| Field | Description |
|---|---|
| Create task / Assign: user | Assign the lead to this user. If you choose a user, the team is ignored. |
| Assign: or team | Assign to a member of this team in round robin order. Members are ordered by user number, and the lead goes to the member after the one who was assigned the team's most recently updated lead, wrapping around to the first. If none of the team's members has a lead yet, the first member is chosen. |
The rotation is worked out from the leads already assigned to team members, not from a separate counter, so a manual reassignment of a team member's lead moves the rotation point. The team drop-down in the form still carries an older label that mentions the member with the fewest open leads; the actual behavior is round robin. If the team has no members, the action is skipped. You must choose a user or a team. An "Assigned by automation" note is added to the lead's timeline. The assigned user is not sent an email notification.
Examples
| Goal | Trigger | Action |
|---|---|---|
| Call every new lead | New lead | Create task "Call new lead", due in 1 hour |
| Spread leads across a team | New lead | Assign: team |
| Start nurturing after contact | Stage change: moved to Contacted | Enroll in campaign |
| Re-engage quiet leads | No activity for 14 days | Create task "Check in with lead" |
| Chase late follow-ups | Task overdue, 24 hours | Change stage to a "Needs attention" stage |