Automations
Automations fire when a lead is created. They evaluate rules and execute actions — sending emails, notifying your team, hitting webhooks, or scheduling a drip sequence.
How automations work
When a visitor submits a form and becomes a lead, VisitorLoop:
- Finds all enabled automations in your org whose trigger matches the lead's widget.
- For each automation, evaluates all rules top-to-bottom.
- For each rule that matches, executes its actions in order.
If no rule matches the lead, the run is recorded as no_match. Add a rule with no conditions to act as a catch-all fallback.
Trigger
Every automation has one trigger: Lead submitted. You can scope it to:
- Any widget — fires for every new lead in your org.
- Specific widget — fires only when a lead comes from the chosen widget.
Rules
A rule is a set of conditions (optional) plus a list of actions. Rules are evaluated in the order they appear. The first matching rule runs; remaining rules are skipped.
Conditions
Conditions filter which leads the rule applies to. Each condition tests a field value:
| Operator | Matches when… |
|---|---|
| equals | field exactly equals the value |
| not equals | field does not equal the value |
| contains | field contains the value (substring) |
| not contains | field does not contain the value |
| is empty | field is blank or missing |
| is not empty | field has any value |
The field name should match a form field key, e.g. email, name, company, or any custom field. Set Match to All conditions (AND) or Any condition (OR).
Leave conditions empty to match every lead that reaches this rule — useful as a catch-all final rule.
Actions
Send email
Sends an email to the lead using one of your Email Templates. Set an optional Reply-to address so replies land in your inbox instead of the sending domain.
Notify team
Sends a plain-text notification email to an internal address (e.g. your sales inbox). Useful for alerting the team when a high-value lead submits.
Send webhook
POSTs the lead's data as JSON to a URL you specify. Use this to push leads into a CRM, Zapier, n8n, or any other system. The payload includes all lead fields and personalisation variables.
Delay
Waits a number of days before executing subsequent actions in the same rule. A delay does not block other rules from running — it schedules the remaining actions in the background.
Delays create scheduled actions
ScheduledAction queue with an executeAt timestamp. A cron job processes them every ~15 minutes. Failed actions are retried automatically up to 3 times (30 min → 2 h → 8 h backoff).Building a drip sequence
Create three email templates: a welcome email, a follow-up, and a final email.
Open an automation and add a rule. Leave conditions empty to match all leads.
Add actions in this order:
Send email (welcome) → Delay 3 days → Send email (follow-up) → Delay 4 days → Send email (final)
Save and enable the automation. New leads will receive the full sequence automatically.
AI sequence generator
Click ✨ Generate with AI inside a rule's actions panel. Describe the sequence in plain English:
"Welcome home buyers, follow up on day 3 asking if they have questions, final tip on day 7."
The AI generates the full action list — complete with new email templates and the correct delays between them. Review the actions, make any edits, then save.
Automation runs
The Activity tab in the automation editor shows a history of all runs. Each run records:
- Which lead triggered it.
- Which rule matched (or
no_matchif none did). - The result of each action (
okorfailed, with a detail message).
No-match nudge
no_match results and you have no catch-all rule, the editor will display an amber warning suggesting you add a fallback rule.Enabling and disabling
Toggle the Enabled switch in the automation editor to pause all future runs without deleting the automation. Disabling does not cancel already-scheduled delayed actions.