Automation Triggers
A trigger is the event that starts an automation. You choose one trigger per automation. Here is a full reference for every trigger available.
New Lead Receivedโ
Fires when: A new lead record is created in your workspace (from any source).
Optional filter:
- Filter by Source(s) โ restrict the trigger to specific sources (e.g. only fire for Facebook leads). Leave blank to fire for all sources.
Use cases:
- Send an immediate welcome email to every new lead
- Assign leads from a specific source to a dedicated team member
- Auto-tag leads by source for segmentation
Lead Stage Changedโ
Fires when: A lead moves from one pipeline stage to another.
Optional filter:
- From Stage โ only fire when moving out of this specific stage (leave blank for any)
- To Stage โ only fire when moving into this specific stage (leave blank for any)
Use cases:
- Send a proposal email when a lead enters the "Proposal Sent" stage
- Notify the sales manager when any lead enters the final stage
Lead Assigned to Userโ
Fires when: A lead is assigned to any team member (assigned_user_id is set or changed).
No additional configuration required.
Use cases:
- Notify the assigned user via Slack or internal notification
- Send the lead a personal introduction email from the assigned rep
Tag Added to Leadโ
Fires when: A specific tag is applied to a lead.
Required configuration:
- Tag Name โ the exact tag that must be added to trigger the automation
Use cases:
- When tag "hot-lead" is added, immediately assign to senior rep and notify via Slack
- When tag "webinar-attendee" is added, enroll in a post-webinar email sequence
Lead Score Crosses Thresholdโ
Fires when: A lead's score crosses a specified threshold (going above or below).
Required configuration:
- Score Threshold โ the score value to watch (e.g. 50)
- Crosses โ "Above threshold" or "Below threshold"
Use cases:
- When score goes above 80, assign to the top sales rep
- When score drops below 20, add a "needs-nurturing" tag
No Activity (Time-based)โ
Fires when: A lead has had no recorded activity for a specified time period.
Required configuration:
- No Activity for โ number (e.g. 3)
- Unit โ Hours or Days
Use cases:
- If no activity for 3 days, send a follow-up email
- If no activity for 7 days, add a "stale-lead" tag
This trigger requires the cron job to be running. It checks periodically for qualifying leads.
Form Submittedโ
Fires when: A LeadHub form is submitted.
Optional filter:
- Form โ restrict to a specific form (leave blank for any form submission)
Use cases:
- Immediately after form submission, send a confirmation email
- When the "Demo Request" form is submitted, assign to the sales team
Manual Triggerโ
Fires when: An admin manually runs the automation from a lead's detail view.
No automatic firing โ must be triggered by a team member for a specific lead.
Use cases:
- One-click follow-up sequence
- Ad-hoc re-engagement workflow
To run a manual automation on a lead:
- Open the lead detail view.
- Click Actions โ Run Automation.
- Select the automation and confirm.