Reference
Automation steps
Reference for every automation step, from send email, time delays, wait until and conditions to tags, scores, audiences, webhooks and other automations, plus branches and step failures.
Steps are what a run does after its trigger fires. This page lists every step by context with its settings and rules, explains how steps connect into branches, and shows what happens when a step fails.
Add and configure steps
On the automation’s Editor tab (available while the automation is a draft or paused):
- Add a step: select the plus button below the last step, below an output of a branching step such as Yes or No, or on a line between two steps. Search the picker or pick from its sections: Messages, Timing, Logic, Contact, Lists, Automations and Integrations.
- Configure a step: select it on the canvas. Its settings open in a side panel, and a short summary shows under the step’s name. Once the step has run, a Stats tab appears next to Configure.
- Remove a step: select it and select Delete step in the side panel.
- Save: select Save. Steps with problems are highlighted with an error count.
Steps by context
| Step | API key | Contact | Event (API) | |
|---|---|---|---|---|
| Send email | send_email |
Yes | Yes | Yes |
| Time delay | wait |
Yes | Yes | Yes |
| Wait until | wait_until |
Yes | Dates only | Dates only |
| Condition (If/Else) | condition |
Yes | Yes | Yes |
| Goal | goal |
Yes | ||
| End automation | end_run |
Yes | Yes | Yes |
| Add tags and Remove tags | add_tag, remove_tag |
Yes | ||
| Update score | update_score |
Yes | ||
| Update contact fields | edit_contact |
Yes | ||
| Add to audience | add_to_audience |
Yes | ||
| Remove from audience | remove_from_audience |
Yes | ||
| Subscribe / unsubscribe | update_subscription |
Yes | ||
| Start automation | run_automation |
Yes | Yes | Yes |
| Remove from automations | exit_automation |
Yes | ||
| Webhook | call_webhook |
Yes | Yes | Yes |
| Forward email | forward_email |
Yes | Yes | |
| Add to suppressions | add_to_suppressions |
Yes | Yes | |
| Remove from suppressions | remove_from_suppressions |
Yes | Yes | |
| Create contact | create_contact |
Yes | Yes | |
| API-only steps | experiment, end |
API | API | API |
Step settings can include placeholders such as {{contact.first_name}}, {{cf.plan}}, {{global.webinar_date}} or {{payload.object.to}}, filled in for each run. See Data available to steps.
Send email
Sends an email built from one of your templates.
| Setting | Required | Notes |
|---|---|---|
| Email template | Yes | The template to send. With the API, template_id takes a tem_ ID or an alias, which uses the published version. |
| Email type | No | Marketing (default in Contact automations) or Transactional (default elsewhere). Email steps saved before the Email type setting existed are set to Transactional, so they keep sending as before. API: email_type. |
| To (recipient) | Email and Event contexts | The address to send to. Contact automations always send to the run’s contact. |
| Subject | No | Overrides the template’s subject. Temple syntax works, for example {{first_name|"there"}}. |
| From name | No | The sender name inboxes show, such as your business name. It goes on the From email override or the template’s sender, replacing any name they have. Without a name, many inboxes show the start of the address, like “info”. API: from_name. |
| From email | No | Overrides the template’s sender address. API: from, which also takes a name, for example "Acme" <hello@acme.com>. |
| Reply to | No | Overrides the template’s reply-to address. Placeholders work, for example {{cf.account_manager_email}}. |
Marketing emails:
- Skip contacts who unsubscribed: from all marketing email, from every audience they’re on, or from the audience that started the run. The step completes with the outcome
skipped, uses no credits and the run continues. - Get an unsubscribe link and headers, like campaign emails:
{{unsubscribe_url}}in the template links to the unsubscribe page, and the email hasList-Unsubscribeand one-clickList-Unsubscribe-Postheaders. Unsubscribing there unsubscribes the contact from all their audiences and from all marketing email.
Transactional emails are always sent, even to unsubscribed contacts, without unsubscribe headers. Use them only for receipts, password resets and similar messages the contact needs.
Rules for both:
- The template is rendered with Temple. In Contact automations, the contact’s fields are available directly:
{{first_name}},{{email}},{{cf.plan}},{{custom_fields.plan}},{{tags}}and{{score}}. Every context also has{{contact.*}},{{global.*}}(global values),{{payload.*}}and{{meta.*}}. - Loads and clicks are tracked with the sending domain’s tracking settings when the domain has a verified tracking CNAME, like emails sent with the API. With the API,
tracking: { "loads": false, "clicks": true }overrides the domain. Email steps saved before 2026-10-20 have tracking off. - The sender must be on a verified domain. The From email override or the template’s sender must use a domain verified in the workspace. Save checks overrides, and the step fails at run time if the domain isn’t verified.
- A subject and content are required, from the template or the overrides.
- Each email costs 1 credit, on top of the 3 credits for the run.
- Suppressed addresses are still blocked at delivery, and sandbox workspaces can only send to members’ account addresses.
The step’s Stats follow each email it sent through Accepted, Delivered, Opened and Clicked, and count bounces, failures, complaints and unsubscribes.
Time delay
Pauses the run for a fixed time before the next step.
| Setting | Notes |
|---|---|
| Duration and Unit | Minutes, Hours or Days. The longest delay is 30 days. With the API, set seconds, up to 2592000. |
While a run waits, it stays Running and the step shows as waiting. Pausing the automation doesn’t interrupt waiting runs.
Wait until
Pauses the run until something happens. Choose what to wait for in Wait until:
| Mode | API mode |
Waits until | Outputs |
|---|---|---|---|
| A date | date |
A date and time, with an optional offset | On date, and Date passed if you choose to branch |
| Something happens | event |
An event for the contact, such as a click, a tag or a purchase | Happened and Timed out |
| The contact matches a condition | condition |
The contact matches rules, such as “has tag registered” |
Happened and Timed out |
Something happens and The contact matches a condition need a Contact automation.
Wait for a date
| Setting | Notes |
|---|---|
| Date | A date on the contact (a Date custom field, or when the contact was created), A global value (a global value of type Date or Date and time, such as webinar_date), A fixed date (UTC) or A date in the trigger data (a path in the payload). |
| Offset, Unit and When | For example 1 days before, for “a day before the webinar”. 0 waits for the date itself. Units: minutes, hours, days, weeks, months. |
| At time and Timezone | Optional. Waits until that time of day on the (shifted) date, in the timezone, for example 09:00 in Europe/Prague. Date-only values without a time wait until midnight. |
| If the date already passed or is empty | Continue right away (default) or Take the “Date passed” branch, which adds a Date passed output, for example to send latecomers a recording instead of a reminder. |
The date is read when the run reaches the step. Changing a global value later changes the wait only for contacts who arrive after the change. Waits can last up to 365 days.
With the API: { "mode": "date", "date": { "type": "global", "key": "webinar_date" }, "offset": { "amount": 1, "unit": "days", "direction": "before" }, "time": "09:00", "timezone": "Europe/Prague", "if_passed": "branch" }. date.type is contact (with field, such as custom_fields.renewal_date), global (with key), fixed (with value) or payload (with path).
Wait for an event or a condition
- Wait for takes the same events as triggers: Link clicked, Email opened, Tag added, Custom event (on Pro, Business and Custom plans, with an optional filter on its properties), Contact updated (a field changing), Score changed, Added to audience and more, with their options. Only events for the run’s contact count. Placed an order and Abandoned a cart (Commerce) and Added to segment and Removed from segment (tracked segments) are in alpha for the Emailit team, like those features.
- Conditions use the same rules as the Condition step. They’re checked when the run arrives, and again every time the contact changes: fields, tags, score or audiences.
- Give up after a while sets a timeout, after which the run continues on Timed out. Without it, the run waits up to 365 days before timing out.
When the event happens or the condition matches, the run continues on Happened. With the API, the outputs are the branches matched and timeout:
{ "mode": "event", "event": { "event": "contact.clicked_in_email", "automation_id": "aut_3Mv8Xq2nKp5Lt" }, "timeout": { "amount": 2, "unit": "days" } }Condition (If/Else)
Sends the run down the Yes branch when the rules match, or the No branch when they don’t. Each rule picks what to Check, then a condition and a value:
| Check | Conditions | Example |
|---|---|---|
| Contact field | Text: is, is not, contains, starts with, is any of… Dates: is before/after, has passed, is within the last/next N days… | Email ends with @acme.com |
| Custom field | Matching the field’s type: text, number (is at least, is greater than…), date, true/false, options | Purchased is false |
| Tag | has tag, does not have tag, has any of, has none of, has any tag, has no tags | has tag customer |
| Audience | is subscribed to, is not subscribed to, is in (any status), is not in | is subscribed to Webinar registrants |
| Lead score | is at least, is at most, is greater than, is less than… | is at least 50 |
| Email engagement | opened, did not open, clicked, did not click | clicked the email from a step send_email-1 |
| Global value | By the value’s type | Offer deadline has passed |
| Trigger data | Text and number conditions on a payload path | payload.object.total is greater than 100 |
| Segment (alpha) | is in, is not in | is in VIP customers |
| Purchases (alpha) | Number of orders, total spent, average order value, first, last and expected next order, last active on site, churn risk, purchased, viewed a product, used a coupon, cart | Purchased has, in the last 30 days |
- Match all rules or any rule. Add group adds a group of rules with its own match mode, for example “has tag
vip, and (score is at least 50 or clicked the last email)”. Groups nest up to 3 levels. - Email engagement checks an email sent in this run, the email from a step, any email from this automation, or any email to the contact in the last N days (up to 365). Opens need tracking on the sending domain.
- Empty values and lists: a field that doesn’t exist counts as empty text, number comparisons on an empty value are false, and an empty list counts as not set. contains on a list matches whole items, comma-separated values in is any of are a list, and a group with no rules matches.
- Can get marketing email is true when the contact hasn’t unsubscribed from everything and is subscribed to at least one of their audiences (or has none).
- In Email automations, Trigger data lists the fields of the trigger’s event.
- Segment and Purchases are in alpha for the Emailit team, like segments and Commerce. Segment checks any segment, tracked or not, against its rules right then. Purchases uses the same rules as the segment builder’s commerce fields, so a condition and a segment always agree. Automations that already use them keep working for everyone.
With the API, config.filter is { "match": "all", "rules": [...] }, and a rule is { "field", "operator", "value" } or a nested { "match", "rules" } group:
field |
operator |
value |
|---|---|---|
email, first_name, last_name, created_at, unsubscribed, subscribed, score, custom_fields.<key>, global.<key>, payload.<path>, meta.<path> |
equals, not_equals, contains, not_contains, starts_with, ends_with, in, not_in, is_set, is_not_set, greater_than, less_than, greater_or_equal, less_or_equal, is_true, is_false, before, after, on, is_past, is_future, within_last, within_next, more_than_ago, more_than_from_now |
The value to compare. Day operators take a number of days or { "amount", "unit" }. |
tags |
contains, not_contains, in, not_in, is_set, is_not_set |
A tag, or a list for in and not_in. |
audience |
is_subscribed, is_not_subscribed, is_member, is_not_member |
The audience ID (aud_…). |
engagement |
opened, not_opened, clicked, not_clicked |
"run", "automation", { "scope": "step", "step": "<step key>" }, { "scope": "any", "days": 30 } or { "scope": "campaign", "campaign_id": "cmp_…" }. |
segment (alpha) |
is_member, is_not_member |
The segment ID (seg_…). |
commerce.orders_count, commerce.total_spent, commerce.average_order_value (alpha) |
equals, not_equals, greater_than, greater_or_equal, less_than, less_or_equal, between |
A number, or [from, to] for between. |
commerce.first_order_at, commerce.last_order_at, commerce.expected_next_order_at, commerce.last_active_at (alpha) |
on, before, after, between, within_last, within_next, more_than_ago, is_set, is_not_set |
A date (YYYY-MM-DD), [from, to], or a number of days. |
commerce.churn_risk (alpha) |
in, not_in |
A list of low, medium, high. |
commerce.purchased, commerce.viewed_product, commerce.used_coupon (alpha) |
has, has_not |
Optional { "days", "product_ids", "categories", "min_count" }, or { "days", "coupon" } for coupons. |
commerce.cart (alpha) |
has_open_cart, has_no_open_cart, has_abandoned_cart |
Optional { "days" } for has_abandoned_cart. |
Segment and commerce rules from anyone outside the Emailit team return 403 with error segments_alpha or commerce_alpha, unless the automation already has them.
A branch with no step ends the run there.
Goal
A goal is a point in the flow that runs jump to as soon as the contact meets it, wherever they are: the run skips the waits and steps in between and continues after the goal. Use it for “they bought: stop the reminders, send the thank-you”. Goal steps are included with Pro, Business and Custom plans; on Pay as you go, an automation that adds one can’t be saved. See Goals.
| Setting | Notes |
|---|---|
| Goal is met when | Something happens (an event, as in Wait until) or The contact matches a condition. |
| When a contact reaches the goal without meeting it | Continue anyway (default), Wait until the goal is met (up to 365 days, then the run ends), or End the automation for them. |
End automation
Ends the automation for the contact at this point. Steps running at the same time on other branches stop too. The run’s status is Completed.
Add tags and Remove tags
Contact context. Adds or removes one or more tags. Tags are stored in lowercase and can be up to 64 characters. Changes send a contact.updated event, so Tag added and Tag removed triggers, waits and goals react to them.
Update score
Contact context. Add, Subtract or Set to a number of points on the contact’s lead score. Use it to score behavior, for example +10 after a click. Score changed triggers, waits and goals react to it.
Update contact fields
Contact context. Changes one or more fields of the run’s contact. Add a row per field:
| Field | Changes |
|---|---|
| First name, Last name, Email | Set to a value, or Clear. The email can’t be cleared or set to an address another contact uses. |
| Unsubscribed from everything | Set to Yes or No: the contact’s marketing status. |
| A custom field | Set to a value, converted to the field’s type (number, date as YYYY-MM-DD, true/false, options), Clear to remove it, or for number fields Increase by and Decrease by. |
Values can use placeholders, for example {{payload.object.audience.name}}. With the API, fields is a list of { "key", "value", "operation" } with operation set to set, clear, increment or decrement. The change sends a contact.updated event, so Contact updated triggers, waits and goals react to it. Steps saved before 2026-10-20 send no event (emit_events: false with the API).
Add to audience
Contact context. Subscribes the run’s contact to the Audience you choose. If the contact had unsubscribed from it, they’re subscribed again. The step fails if the audience has reached its subscriber limit. It starts Added to audience automations, except this one. Steps saved before 2026-10-20 send no events and start no automations (emit_events: false).
Remove from audience
Contact context. Deletes the contact’s membership in the Audience, like Remove from audience in the dashboard, and starts Removed from audience automations. To keep the person on the audience as unsubscribed instead, use Subscribe / unsubscribe. Steps saved before 2026-10-20 work as they did then: the contact stays on the audience as unsubscribed, and no event is sent. With the API, mode (remove or unsubscribe) and emit_events set this.
Subscribe / unsubscribe
Contact context. Changes the contact’s subscription the same way the dashboard and unsubscribe links do:
| Action | From | Effect |
|---|---|---|
| Unsubscribe | One audience | Turns the subscription to that audience off. |
| Unsubscribe | Every audience they’re on | Turns all of the contact’s subscriptions off. |
| Unsubscribe or Subscribe | All marketing email (global status) | Sets the contact’s marketing status. |
| Subscribe | One audience | Subscribes them, or turns a subscription back on. |
Webhooks and other automations get the usual subscriber.updated, subscriber.created and contact.updated events.
Start automation
Starts a run of another automation for the same contact (or with the same payload outside Contact automations). The other automation must be running, and its run costs its own 3 credits. With Move the contact, the current run ends after starting the other one. An automation can’t start itself.
Remove from automations
Contact context. Cancels the contact’s runs in progress in the automations you pick, or in Every other automation, for example so buyers leave every promotional sequence. The current run continues.
Webhook
Sends an HTTP request to another system, such as your CRM, Slack or Zapier.
| Setting | Notes |
|---|---|
| Method and URL | POST by default. Placeholders work in the URL. Private and internal addresses are blocked. |
| Headers | One per line, Name: value. |
| Body | JSON with placeholders, for example { "email": "{{contact.email}}" }. Leave it empty to send the automation, the run, the contact (with tags and score) and the trigger data. |
| Signing secret | Signs the body in X-Emailit-Signature: t=<unix time>,v1=<HMAC-SHA256 of "t.body">, so you can check the request came from Emailit. |
| Fail the step when the response isn’t 2xx | Off by default: the result (2xx, 4xx, 5xx, timeout or network_error) is only recorded, and the run continues. |
Requests time out after 10 seconds and follow up to 3 redirects, to public addresses only. The response status and the first 10,000 characters of the body are saved in the step’s output.
Forward email
Email and Event contexts. Sends a copy of the run’s email, with its original content and attachments, to the address in Forward to. The subject becomes “Fwd: “ plus the original subject. The email must come from a verified sending domain in the workspace, and each forward costs 1 credit. See Forward with automations.
Add to suppressions
Email and Event contexts. Adds an address to your suppression list with type recipient, which blocks all sending to it, and the Reason you enter (default automation). In Email automations, the address is the email’s recipient. In Event automations, set email with the API, for example {{payload.email}}. The step sends a suppression.created event.
Remove from suppressions
Email and Event contexts. Removes the address from the suppression list: the email’s recipient in Email automations, or email set with the API in Event automations.
Create contact
Email and Event contexts. Creates a contact and, if you pick an Audience (optional), subscribes it there.
- In Email automations, the contact is the email’s recipient address. For received emails, that’s the address the email was sent to. To create a contact for the sender instead, set
emailto{{email.mail_from}}with the API. - In Event automations, set
emailand optionallyfirst_namewith the API. - If the contact already exists, it’s kept as it is and only subscribed to the audience.
- The step sends
contact.createdandsubscriber.createdevents, so it starts Contact created and Added to audience automations. Steps saved before 2026-10-20 send none (emit_events: false).
API-only steps
These steps can be added with the API but not in the dashboard editor yet.
| Step | API key | Config | What it does |
|---|---|---|---|
| Random split | experiment |
variants: list of { "key", "weight" }, optional control |
Sends each run down one branch at random, in proportion to the weights. Each variant’s branch is named after its key. When a variant’s branch ends, the run continues on the step’s default branch. |
| End | end |
None | Marks the end of a branch. Other branches keep running. |
Branches and connections
With the API, an automation is a list of steps, each with a unique key, and a list of connections from one step key to the next:
{
"steps": [
{ "key": "trigger-1", "type": "trigger", "trigger": "contact.added_to_audience", "config": {} },
{ "key": "is-pro", "type": "action", "action": "condition", "config": {
"filter": { "match": "all", "rules": [{ "field": "custom_fields.plan", "operator": "equals", "value": "pro" }] }
} },
{ "key": "send-pro", "type": "action", "action": "send_email", "config": { "type": "template", "template_id": "welcome-pro" } },
{ "key": "send-free", "type": "action", "action": "send_email", "config": { "type": "template", "template_id": "welcome-free" } }
],
"connections": [
{ "from": "trigger-1", "to": "is-pro", "branch": "default" },
{ "from": "is-pro", "to": "send-pro", "branch": "yes" },
{ "from": "is-pro", "to": "send-free", "branch": "no" }
]
}branchisdefaultfor a normal next step,yesornoafter a condition,matchedortimeoutafter Wait until an event or a condition,defaultorpassedafter Wait until a date, and a variant key after a random split.- Branching steps only follow the branch they picked. A
defaultconnection out of a condition, for example, is never followed. - A step with several outgoing connections on the same branch starts all of them, and the branches run side by side.
- Every step must be reachable from a trigger. In Contact and Email automations with several triggers, all triggers must connect to the same first step.
- Send
stepsandconnectionstogether when you update an automation. Steps whose keys don’t change keep their history and stats.
When a step fails
By default, a failed step fails the whole run, and the remaining steps don’t run. The error is saved on the step, and you can read it in the run’s details on the Runs tab. Set When a step fails to Skip the step and continue on the Settings tab (on_step_failure: "skip" with the API) to let runs continue past failed steps instead; after a failed condition, the run continues on No.
| Error | Cause |
|---|---|
send_email: Template '…' not found or not published |
The template was deleted, or the alias has no published version. |
send_email: Sending domain is not verified or not found |
The sender’s domain isn’t verified in the workspace. |
send_email: Unable to determine recipient address |
To (recipient) is empty, or the contact no longer exists. |
send_email: Insufficient credits (…) |
The workspace ran out of credits. |
Pro includes 50,000 subscribers per audience. (or your plan’s limit) |
An Add to audience or Create contact step hit a full audience. |
edit_contact: another contact already uses … |
Update contact fields tried to set an email another contact has. |
call_webhook: URL resolves to a private/reserved IP address |
The webhook URL points to an internal address. |
forward_email: Source email has no raw content to forward |
The email’s content was already removed by your data retention settings. |
See Runs and stats for how to find and fix failed runs.