Skip to content
Docs

OverviewBeta

Automations run steps such as sending an email, waiting or tagging a contact when a trigger fires. Learn contexts, exits, goals, statuses, runs, credits and the API.

Updated Oct 20, 2026

An automation is a workflow that starts on its own: when a trigger fires, such as a contact joining an audience, getting a tag or reaching a lead score, Emailit starts a run that works through the steps you’ve connected, such as sending an email, waiting until a date, checking a condition or updating the contact. Use automations for welcome and onboarding sequences, cart and webinar reminders, lead scoring, birthday emails, forwarding and alerts.

How it works

  1. A trigger fires. Every automation starts with a trigger, for example Added to audience or Tag added. Optional settings and filters narrow it down.
  2. Emailit starts a run for the contact or email that caused it, and charges 3 credits.
  3. The run works through the steps connected to the trigger. Time delay and Wait until steps pause it, Condition steps send it down a Yes or No branch, and action steps send emails, change the contact or call other systems.
  4. The run ends when it reaches the last step of its branch, an End automation step, or an exit condition, or fails if a step fails.

Two things can move a run without it reaching the next step: an exit condition takes the contact out as soon as it matches (for example when they buy), and a goal step pulls the run forward to the goal when the contact meets it. Goal steps are included with Pro, Business and Custom plans. See Exit conditions and goals.

You build the flow on a canvas in the dashboard, or send it to the API or the MCP server as a list of steps and connections. See Triggers and Steps.

Contexts

Each automation has a context, which decides what a run is about and which triggers and steps are available. You choose it when you create the automation, and it can’t be changed later.

Context Label Each run is about Good for Triggers
Contact Easy One contact Welcome series, onboarding, cart and webinar reminders, lead scoring Audiences, tags, score, contact changes, dates, opens and clicks, forms, custom events
Email Medium One email Reply handlers, auto-forwarders, bounce alerts Email events, such as delivered, bounced or received
Event Advanced One API call API-driven flows, custom integrations A manual trigger you call with the API

In the dashboard, the Event context shows a Soon badge and can’t be selected yet. You can create Event automations with the API.

Create an automation

  1. Start. Go to Email MarketingAutomations and select New automation.

  2. Choose the context. Pick Contact or Email.

  3. Choose a template. Pick one of the ready-made recipes or Start from scratch for a blank canvas with just a trigger. Add the first step with the plus button under the trigger.

  4. Name it. Enter a Name and an optional Description, then select Create. The automation opens as a draft.

  5. Build the flow. On the Editor tab, select the trigger and each step to configure them, and add steps with the plus buttons. Select Save.

  6. Set the exits. On the Settings tab, add exit conditions, for example “a purchase happens”, and choose what happens when a contact is already in the automation. In new Contact automations, a contact’s run ends when they’re removed or unsubscribed from the audience that started it.

  7. Start it. Select Start. From now on, every matching trigger starts a run.

The list page has tabs for Contact, Email and Event automations and shows each one’s Name, Status, Last triggered time and Created date.

Statuses

Status Triggers start runs Editable in the dashboard How to get there
Draft No Yes Every new automation starts as a draft.
Running Yes No Start a draft or paused automation.
Paused No Yes Pause a running automation. Start resumes it.
Stopped No No Only with the API’s stop endpoint, which also cancels every run in progress.

Pausing stops new runs from starting, but runs already in progress continue, including those waiting in a Time delay or Wait until step. Their exit conditions and goals keep working while the automation is paused. Delete, in the menu at the top of the automation, removes it in any status.

Editing rules

The Editor tab is only available while the automation is a draft or paused. On a running automation, the tab shows Pause to edit. The Settings tab can be changed in any status, and new exit conditions apply to runs already in progress.

Save checks the whole flow and highlights the steps that need attention, for example a Send email step without a template or a Wait until step without a date. Fix them and save again before you select Start: starting a saved flow doesn’t run the checks again. With unsaved changes, Start saves them first, runs the same checks and only starts when they pass.

Runs

A run is one pass through the automation for one contact, email or API call. Each run has a status:

Run status Meaning
Running The run is working through its steps or waiting.
Completed The run reached the end of its path, an End automation step, or moved to another automation.
Failed A step failed, or the workspace didn’t have enough credits when the run started.
Canceled An exit condition matched, the contact left the audience, someone canceled the run or removed the contact, another automation removed them, or the automation was stopped.

By default, every trigger starts a new run, even if the same contact or email already has one in progress. The same event never starts two runs of one automation. You can cancel a run from the Runs tab. See Runs and stats for the run history and debugging.

Credits

Action Credits
Each run 3, charged when the run starts
Each email sent by a Send email step 1
Each email sent by a Forward email step 1

Marketing emails skipped because the contact unsubscribed don’t use credits. If the workspace doesn’t have 3 credits when a trigger fires, the run is created with status Failed and the reason insufficient_credits in its meta. If credits run out in the middle of a run, the Send email or Forward email step fails. See Credits.

Use the API

The Automations API manages automations and their runs. It needs an API key with Full Access. The same operations are tools on the MCP server, so an AI assistant can build a whole workflow from a description.

Endpoint Use it to
Create, update, retrieve, list and delete Manage automations. Steps and connections are sent together.
Start, pause and stop Change the status.
Trigger a run Fire a Manual trigger, with an optional payload. The automation must be running. This is only possible with the API.
Cancel a run and remove a contact Stop one run, or every run of one contact in this automation.
List runs, a contact’s runs, retrieve a run, statistics and step statistics Read the run history and per-step results.

Automation settings, also on the Settings tab:

Setting Default Effect
exit_conditions none Cancel a contact’s run as soon as an event or a condition matches. See Exit conditions.
exit_on_audience_removal false (true for Contact automations created in the dashboard) Cancel a run when the contact is removed or unsubscribed from the audience that started it.
allow_reentry true Set to false to skip new runs for a contact or email that already has a run in progress.
max_concurrent_runs 0 (no limit) Skip new runs while this many runs are in progress.
cooldown_seconds 0 Skip new runs for a contact or email that started a run within this many seconds.
on_step_failure stop stop fails the run when a step fails. skip continues after the failed step (a failed condition continues on No).

Skipped runs aren’t created and don’t use credits.

Terminal
curl https://api.emailit.com/v2/automations \
  -X POST \
  -H "Authorization: Bearer $EMAILIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "context": "contact",
    "name": "Cart reminder",
    "settings": {
      "exit_on_audience_removal": true,
      "exit_conditions": [{ "event": "contact.tag_added", "tag": "customer" }]
    },
    "steps": [
      { "key": "trigger-1", "type": "trigger", "trigger": "contact.added_to_audience", "config": { "audience_id": "aud_5hJ2kL8mNp4Qr" } },
      { "key": "wait-1", "type": "action", "action": "wait", "config": { "seconds": 3600 } },
      { "key": "send_email-1", "type": "action", "action": "send_email", "config": { "type": "template", "template_id": "cart-reminder" } }
    ],
    "connections": [
      { "from": "trigger-1", "to": "wait-1", "branch": "default" },
      { "from": "wait-1", "to": "send_email-1", "branch": "default" }
    ]
  }'

The automation is created as a draft. Call Start an automation to turn it on.

Next steps

Every trigger and its options.
Every step, its settings and how branches work.
Take buyers out, jump runs to a goal.
The ready-made templates.
Follow, cancel and debug runs.
Label and score contacts for your flows.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.