Skip to content
Docs

Reference

Reference for every automation trigger by context, with their options and filters, what fires them, and the trigger keys to use with the API.

Updated Nov 20, 2026

A trigger decides when an automation starts a run. This page lists every trigger available in each context, what fires it, its options, and the key you use for it in the API.

How triggers work

  • One trigger per automation in the dashboard. Select the trigger on the canvas and change it with Trigger type. With the API, Contact and Email automations can have several triggers, as long as they all connect to the same first step. Event automations have exactly one. Each trigger that fires starts its own run, so one signup can start two: a form that adds the contact to an audience fires Form submitted and Added to audience together. For one run, set Same contact again while a run is in progress to Don’t start another run on the Settings tab (allow_reentry: false).
  • The automation must be running. Triggers in draft, paused or stopped automations are ignored. Events from before you start an automation don’t start runs later.
  • Runs start within seconds. Emailit picks up new events every few seconds. Date triggers are checked every 5 minutes.
  • Contact automations need a contact. An event that can’t be tied to a contact in the workspace, such as an open by an address that isn’t a contact, doesn’t start a run.
  • Automations can start each other. Changes made by a step, such as adding a tag or a contact to an audience, start other automations’ triggers. An automation never starts itself this way, and a chain of automations started by each other stops after 5 links.

Filters

Contact updated, Custom event, Placed an order, Abandoned a cart, Viewed a product, Product back in stock and every email trigger take an optional filter. Each rule compares one field of the event with a value:

  • Operators: Equals, Not equals, Contains, Not contains, Greater than, Less than, Is set, Is not set, In, Not in, Starts with and Ends with. Greater than and Less than compare numbers. The rest compare text and are case-sensitive.
  • Match mode: All rules match or Any rule matches.

With the API, a filter is { "match": "all", "rules": [{ "field": "...", "operator": "equals", "value": "..." }] } in the trigger’s config.filter, with match set to all or any. Fields are paths into the event’s object, for example to, link.url or, for a custom event, properties.total. To check the contact itself (tags, audiences, score), add a Condition step after the trigger.

Contact triggers

Trigger API key Options Starts a run when
Added to audience contact.added_to_audience Audience. Leave it empty for any audience. A contact joins the audience, or is added back after unsubscribing.
Removed from audience contact.removed_from_audience Audience. Leave it empty for any audience. A contact’s membership in the audience is deleted.
Added to segment contact.added_to_segment Tracked segment (required), and whether to include current members A contact starts matching a tracked segment.
Removed from segment contact.removed_from_segment Tracked segment (required) A contact stops matching a tracked segment.
Contact created contact.created None A contact is created.
Contact updated contact.updated Field that changed, optional filter A contact’s fields, custom fields, tags, score or marketing status change.
Tag added contact.tag_added Tag. Leave it empty for any tag. The contact gets the tag.
Tag removed contact.tag_removed Tag. Leave it empty for any tag. The tag is removed from the contact.
Score changed contact.score_changed Crosses and Direction The contact’s lead score changes, or crosses a threshold.
Unsubscribed contact.unsubscribed Audience. Leave it empty for any. The contact unsubscribes from an audience, or from all marketing email.
Email opened contact.loaded_email Only emails sent by this automation The contact loads a tracked email sent to their address.
Link clicked contact.clicked_in_email Link contains, only emails sent by this automation The contact clicks a tracked link in an email sent to their address.
Date in contact field contact.on_date Date field, offset, time, timezone, Repeat A date stored on the contact comes, or is a set number of days away.
Date anniversary contact.date_anniversary Date field, offset, time, timezone Every year on the month and day of a date on the contact.
Custom event contact.on_event Event name. Leave it empty for any. Your app sends a workspace or custom event for the contact with the Events API, such as a purchase. Business and Custom plans.
Form submitted form.submitted Form. Leave it empty for any form. Someone submits a form with an email address.
Placed an order contact.on_purchase Optional filter A contact places a new order.
Abandoned a cart contact.abandoned_cart Optional filter A contact’s cart is abandoned.
Viewed a product contact.viewed_product Optional filter A contact views a product on your site.
Product back in stock contact.back_in_stock Optional filter A product a contact asked about is available again.

Added to audience

Fires when someone is added to an audience from the dashboard (Add subscriber, Add to audience, Add contact with audiences), with the API (Add a subscriber, or Create a contact with audiences), with the Add to audience bulk action, or by another automation’s Add to audience, Subscribe / unsubscribe or Create contact step. Adding back someone who unsubscribed also fires it.

It doesn’t fire for contacts added by a file import or a subscribe URL sign-up, and turning Subscribed back on for an existing subscriber in the dashboard doesn’t count either.

Removed from audience

Fires when a subscriber is deleted: Delete on the audience page, Remove from audience, Delete a subscriber, a contact update whose audiences list leaves the audience out, or another automation’s Remove from audience step. Deleting a contact fires it once for each audience the contact was on. Unsubscribing doesn’t fire it, because the person stays on the audience; use Unsubscribed for that.

To stop runs of a sequence when the contact leaves its audience, you don’t need a second automation: turn on Leave when removed or unsubscribed from the audience that started the run on the Settings tab. See Exit conditions and goals.

Segment triggers

Added to segment and Removed from segment fire when a contact joins or leaves a tracked segment. Like segments, they’re in alpha and open to the Emailit team only. Choose the segment under Tracked segment. Only tracked segments are listed and accepted, because other segments don’t record joins and leaves.

  • When they fire. When a contact changes, its segments are checked again, and runs usually start within a minute. Imports and deleted audiences are checked when they finish. Rules that move with time, such as Created in the last 30 days, are checked by a daily sync at 00:30 UTC.
  • Edits to the segment don’t start runs. Contacts who join or leave because you changed the segment’s source or filters are recorded and sent to webhooks, but don’t start automations.
  • No runs for the first count. Creating a tracked segment, or resuming tracking after an upgrade, records the current members without starting runs.
  • Include current members. On Added to segment, select Also start for contacts already in the segment when the automation is first started to start a run for every current member too. It happens once, on the automation’s first start. Re-entry settings still apply.

In a run, {{payload.object.segment.name}} holds the segment’s name and {{payload.object.reason}} why the contact joined or left: contact, schedule, or existing_member for runs started for the segment’s current members.

With the API, set config.segment_id to the segment’s seg_ ID, and for contact.added_to_segment optionally config.include_current_members: true. A segment that automations use can’t be deleted until you change those automations.

Contact updated

Fires whenever a contact is updated in the dashboard, with the API or by an automation step, including tag and score changes and the Unsubscribe and Resubscribe bulk actions. Field that changed limits it to one field, for example a purchased custom field your CRM sets. The filter can check the current Email, First name, Last name, Unsubscribed and custom fields, and their previous values, listed as Previous email, Previous first name and so on. Previous values are only present for the fields that changed.

For example, to react when a contact moves to the pro plan, add two rules with All rules match: custom_fields.plan Equals pro, and Previous plan (previous.custom_fields.plan) Not equals pro.

Tag added and Tag removed

Fire when a tag is added to or removed from the contact by any route: the dashboard, the API, the MCP server or an automation step. Tags are compared in lowercase, so VIP and vip are the same tag.

Score changed

Fires when the contact’s lead score changes. With Crosses set, it only fires when the score passes that value: going up (Going up, the default) means the old score was below it and the new one is at or above it, so “leads above 50 enter the sales workflow” fires once, not on every point. Going down fires when the score drops below the value.

Unsubscribed

Fires when the contact unsubscribes from an audience (an unsubscribe link, the dashboard, the API or a Subscribe / unsubscribe step) or from all marketing email. With Audience set, it only fires for that audience, and for unsubscribes from everything.

Fire when the contact loads or clicks a tracked email sent to their address: campaigns, API and SMTP email, and automation emails. Tracking needs the sending domain’s tracking settings and a verified tracking CNAME. Only emails sent by this automation limits them to emails from the automation itself, and Link contains to links whose URL contains the text, for example /pricing.

To react to an open or click of an email the run just sent, use a Wait until step with Something happens instead. See Wait until.

Date in contact field and Date anniversary

Pick a Date field, a custom field of type Date such as a renewal date or a birthday, then when to start:

  • Days with Unit (days or weeks) and When (before the date or after the date), for example 3 days before a renewal. 0 means on the date.
  • At time (default 00:00) in Timezone (an IANA name such as Europe/Prague, default UTC).
  • Repeat on Date in contact field: Once, on that date, or Every year (anniversary). Date anniversary always repeats yearly; the year in the field doesn’t matter, so 1990-04-12 starts a run every April 12. In other years, February 29 anniversaries start on February 28.

Emailit looks 5 minutes ahead and starts each run at the minute you set. Each contact gets one run per date (or per year for anniversaries), and each check handles up to 100,000 contacts per automation.

With the API, set config.date_field to the custom field’s key, offset to { "amount": 3, "unit": "days", "direction": "before" }, and optionally time, timezone and repeat: "yearly".

Custom event

This trigger is included with Business and Custom plans. On Pay as you go and Pro, an automation that adds it can’t be saved (403 with "error": "plan_required"). Automations that already use it keep it after a downgrade.

Fires when your app sends a custom event (c: events) or a workspace event (w: events) for the contact with the Events API. Events from the tracking script don’t start runs, because anyone with your public tracking key can name any visitor. Name it in Event name:

  • purchase matches c:purchase and w:purchase.
  • A name with its prefix, like w:webinar.attended, matches only that one.
  • Leave it empty to start on any workspace or custom event.

The field suggests the workspace events you defined and the custom events your workspace sent recently. Under Only when the properties match (optional), filter on the event’s properties, for example properties.total Greater than 100. For a workspace event, the field list shows its defined properties.

The event must name a contact of the workspace by ID or email address. Events from anonymous visitors, or for addresses that aren’t contacts, don’t start runs. In the run, {{payload.object.properties.total}} and the like hold the properties.

Placed an order

Like Commerce, this trigger is in alpha and open to the Emailit team only. Automations that already use it keep running.

Fires once for each new order of a contact, from the Orders API or the tracking script’s purchase command. Orders imported as history and orders without a contact don’t fire it, and updates to an order don’t fire it again. The filter can check the order’s Order total, Currency, Status, Source and Coupon codes, and emails can use the order as {{payload.object.total}}, {{payload.object.external_id}} and so on.

Abandoned a cart

Like Commerce, this trigger is in alpha and open to the Emailit team only. Automations that already use it keep running.

Fires each time a cart is abandoned: a cart of a known contact that has items and hasn’t changed for the delay set in Commerce settings (60 minutes by default). The filter can check Cart total, Currency and Source. In the emails, {{cart}} shows the cart, see Products, coupons and the cart.

Send email steps of a run started by this trigger are skipped once that cart has turned into an order, so buyers don’t get reminders about what they just bought. See the abandoned cart recipe.

The API also accepts contact.visits_url, but nothing fires it yet.

Viewed a product

Like Commerce, this trigger is in alpha and open to the Emailit team only. Automations that already use it keep running.

Fires when a contact views a product on your site, through the tracking script’s product command or the Emailit pixel on Shopify. Anyone with your public tracking key can send views, so only views by a contact who arrived from one of your emails (a signed link) or who subscribed to an audience fire it. The filter can check Product ID (shop), Product title and Price. Emails can use {{payload.object.product.title}}, or show everything the contact looked at with {{products "recently_viewed"}}.

One visit usually has several product views. For browse abandonment, set Wait between runs for the same contact (hours), wait before the email, and exit on Placed an order, as the Browse abandonment template does.

Product back in stock

Like Commerce, this trigger is in alpha and open to the Emailit team only. Automations that already use it keep running.

Fires when a product a contact asked about with the back-in-stock form on your Shopify store is available again, once for each request. The filter can check Product ID (shop), Product title and Variant ID. Emails can use {{payload.object.product.title}}, {{payload.object.product.url}}, {{payload.object.product.image_url}} and {{payload.object.variant.title}}. The Back in stock template sends its email as transactional, because the contact asked for it.

Email triggers

Email triggers fire for emails in your workspace: everything you send with the API or SMTP, campaign and automation emails, and inbound email for Email received. Each run is about one email.

Trigger API key Starts a run when Filter fields
Email delivered email.delivered The recipient’s server accepted the email. From, To, Subject, Status
Email bounced email.bounced The email failed permanently. From, To, Subject, Status
Email failed email.failed The email couldn’t be sent because of an error. From, To, Subject, Status
Email suppressed email.suppressed The email wasn’t sent because the recipient is suppressed. From, To, Subject, Status
Email complained email.complained The recipient reported the email as spam. From, To, Subject, Status
Email received email.received An inbound email arrived. See Inbound. From, To, Subject
Email loaded email.loaded The recipient loaded a tracked email. Recipient, Sender, Subject, IP address, User agent
Email clicked email.clicked The recipient clicked a tracked link. Recipient, Sender, Subject, Link URL, IP address, User agent

The editor also lists Email accepted, Email scheduled, Email attempted and Email rejected. Automations with these triggers can’t be saved yet, so pick one of the triggers above. With the API you can also use email.canceled, which fires when a scheduled or queued email is canceled.

Event triggers

Event automations can only be created with the API for now.

Trigger API key Starts a run when
Manual trigger system.manual You call Trigger a run.
Schedule system.schedule Reserved. Nothing fires it yet, so call the trigger endpoint from your own scheduler, such as a cron job, instead.

Manual trigger

Call the trigger endpoint of a running automation, with an optional payload object:

Terminal
curl https://api.emailit.com/v2/automations/aut_3Mv8Xq2nKp5Lt/trigger \
  -X POST \
  -H "Authorization: Bearer $EMAILIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "payload": { "email": "ada@example.com", "plan": "pro" } }'

The endpoint returns { "message": "Automation trigger dispatched." }, or 422 if the automation isn’t running. It starts a run of that automation only. Steps can read the payload as {{payload.email}}, {{payload.plan}} and so on. Emailit adds automation_id to the payload.

system.manual also works as a trigger in Contact and Email automations created with the API. Include contact_id (a con_ ID) or email_id in the payload to run the automation for that contact or email.

Data available to steps

Step settings, such as the recipient of Send email, the values of Update contact fields or the body of a Webhook, can include placeholders that are filled in for each run:

Placeholder Contains
{{contact.<field>}} The run’s contact in Contact automations, for example {{contact.email}}, {{contact.score}} or {{contact.custom_fields.plan}}.
{{cf.<key>}} A custom field of the contact, for example {{cf.plan}}.
{{tags}} The contact’s tags, comma-separated.
{{global.<key>}} A global value, for example {{global.webinar_date}}.
{{email.<field>}} The run’s email in Email automations, for example {{email.rcpt_to}} or {{email.subject}}.
{{payload.<path>}} The event that started the run. For webhook-style events, the event’s data is under payload.object, for example {{payload.object.to}}. For manual triggers, it’s your payload.
{{meta.<path>}} Extra data Emailit stores about the run.
{{run.id}} The run’s ID (aur_…).

Email templates sent by Send email use Temple with the same data. See Steps.

What a run can do once it starts.
Events that end or move a run.
The events behind contact and email triggers.
Tags and scores for triggers and conditions.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.