Automatic emails
Automatic emails (automations) run when a contact is created. They evaluate rules and execute actions — sending emails, notifying your team, hitting webhooks, or scheduling a drip sequence.
Find them in Emails → Automatic. Click New automatic email, give it a name, and click Create & edit to open the editor.
How automatic emails work
When a visitor submits a form and becomes a contact, MyVisitors:
- Finds all enabled automatic emails in your org whose trigger matches the contact's widget.
- For each one, evaluates all rules top-to-bottom.
- For each rule that matches, executes its actions in order.
If no rule matches the contact, the run is recorded as no_match. Add a rule with no conditions to act as a catch-all fallback.
Trigger
Every automatic email has one trigger: Someone fills in a form. You can scope it to:
- Any widget — fires for every new contact in your org.
- Specific widget — fires only when a contact 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 contacts the rule applies to. Each condition tests a field value:
| Operator | Matches when… |
|---|---|
| equals | field exactly equals the value |
| does not equal | field does not equal the value |
| contains | field contains the value (substring) |
| does not contain | 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. Choose ALL are true (AND) or ANY is true (OR).
Leave conditions empty to match every contact that reaches this rule — useful as a catch-all final rule.
Actions
Send them an email
Sends an email to the contact 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 member
Sends a plain-text notification email to an internal address (e.g. your sales inbox). Useful for alerting the team when a high-value contact signs up.
Send to webhook URL
POSTs the contact's data as JSON to a URL you specify. Use this to push contacts into a CRM, Zapier, n8n, or any other system. The payload includes all contact fields and personalization variables.
Wait X days
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 in Emails → Templates: a welcome email, a follow-up, and a final email.
Open an automatic email and add a rule. Leave conditions empty to match all contacts.
Add actions in this order:
Send them an email (welcome) → Wait 3 days → Send them an email (follow-up) → Wait 4 days → Send them an email (final)
Save it and make sure it's switched on. New contacts will receive the full sequence automatically.
AI sequence generator
Click ✨ Generate with AIinside 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.
Runs
The Runs tab in the editor shows a history of all runs. Each run records:
- Which contact 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.Pausing and turning back on
Use the switch next to each automatic email in Emails → Automatic to pause all future runs without deleting it. A paused one shows Paused. Pausing does not cancel already-scheduled delayed actions.