Skip to content
Docs

Reference

Automations changelog

Changes to Automations: new features, improvements and fixes.

October 2026

  1. Fixed

    API accepts single reply-to addresses, Unix keep_until and one run ID

    REST APITemplatesSuppressionsAutomations

  2. New

    Segments in alpha

    SegmentsCampaignsAutomationsWebhooks

    Segments are now under Email Marketing > Segments in the dashboard. They’re in alpha: open only to the Emailit team while we test them, so customer workspaces don’t see them yet. A segment starts from all contacts or the subscribers of chosen audiences, and narrows them down with groups of rules on contact fields, custom fields and audience membership. Emailit evaluates it whenever it’s counted, listed or sent to, so it’s always current.

    • Campaigns can send to segments, alone or with audiences, and exclude audiences and segments. Exclusions now apply when the campaign sends. If an excluded audience or segment was deleted, Emailit doesn’t send the campaign.
    • Tracked segments on Pro, Business and Custom also record who joins and leaves. Joins and leaves start automations with the new Added to segment and Removed from segment triggers, send the segment.contact_added and segment.contact_removed webhook events, and fill the segment’s Growth chart. You choose tracking when you create a segment.
    • Limits: Pay as you go includes 3 segments, Pro 10 and Business 100, tracked or not. On Custom plans the number is flexible.
    • API and MCP: the Segments API and the segments MCP toolset create, preview and list segments, their contacts and their growth.

    See Segments and Tracked segments.

  3. New

    A/B tests, sending options and reports for campaigns, and Commerce in alpha

    CampaignsAutomationsEvent tracking

    • A/B tests: test up to five versions of a campaign and send the winner by open or click rate. See A/B testing.
    • Sending options: smart sending, skipping unengaged contacts, UTM parameters, tags, and sending throttled, at each recipient’s local time or at their best hour. Recipients’ time zones come from the tracking script. See Sending options.
    • Reports: opens by email client, device and country, a click map, follow-ups to contacts who didn’t open or click, a campaign calendar and Retrieve campaign statistics.
    • Fixed: Send or schedule a campaign, with the API or the MCP server, returns 422 for a campaign that is already sending or was sent, instead of sending it again.

    Commerce in alpha

    Commerce is open only to the Emailit team while we test it, so customer workspaces don’t see it yet. See Who can use Commerce.

    • Shop data: products, orders and carts from the Products, Orders and Carts APIs, which also take Events Only keys, or from the tracking script. Orders are credited to the campaign or automation email the buyer last clicked or opened, and Email Marketing > Commerce shows revenue from email, top products and top campaigns. See Commerce and Connect your shop.
    • In the event log: orders, carts and product views are system events (order.placed, order.updated, cart.updated, cart.abandoned, product.viewed) on the Events page, in contact activity and for webhooks.
    • Products, coupons and the cart in emails: product grids and recommendations, a unique coupon code for every recipient, the contact’s cart and their purchase data. See Products, coupons and the cart.
    • Revenue in campaigns: revenue, orders and conversion rate in reports, and A/B tests won by orders or revenue.
    • Segments and automations: segment rules for orders, spend, churn risk, products bought or viewed, carts and coupons (see Activity rules), and Placed an order and Abandoned a cart triggers with ready-made recipes.
  4. New

    Automations: exit conditions, goals, wait until, tags, lead score and global values

    AutomationsContacts

    • Exit conditions: the new Settings tab ends a contact’s run as soon as something happens (a purchase, a tag, a field change) or the contact matches rules. Leave when removed or unsubscribed from the audience that started the run stops a sequence when the contact leaves its audience, and is on for new Contact automations. See Exit conditions and goals.
    • Goals: a Goal step pulls a run forward as soon as the contact meets it, skipping the waits in between.
    • Wait until: wait for a date (a contact field, a global value or a fixed date, with offsets like “1 day before”, a time of day and a timezone), for an event such as a click or a tag, or for a condition, with a timeout branch.
    • Richer conditions: the If/Else step checks custom fields by type, tags, audience membership, lead score, email opens and clicks, dates and global values, with nested groups.
    • New steps: Add tags, Remove tags, Update score, Subscribe / unsubscribe, Start automation (with Move the contact), Remove from automations, End automation, and Webhook in the dashboard with signing. Update contact fields can clear fields and increase numbers.
    • New triggers: Tag added, Tag removed, Score changed, Unsubscribed, Contact created, Email opened, Link clicked, Custom event and Date in contact field, which now works from the dashboard with offsets, a time and a timezone.
    • Event tracking in automations: the workspace and custom events you send with the Events API start Custom event triggers, optionally only when their properties match, and can end runs, reach goals and resume Wait until steps. Events from the tracking script don’t, because anyone with the public tracking key can name a visitor.
    • Plans: Goal steps, and exit conditions, goals and waits on workspace or custom events, are included with Pro, Business and Custom plans. The Custom event trigger is included with Business and Custom. Automations keep what they already have after a downgrade.
    • Marketing emails from automations skip unsubscribed contacts and get an unsubscribe link, one-click headers and {{manage_subscriptions_url}}, and automation emails are tracked with the domain’s tracking settings. Send email steps in Contact automations are marketing emails by default.
    • Cancel runs from the Runs tab or the API, and remove a contact from an automation with the API.
    • Tags and lead score on contacts, global values for the workspace, and every new step and setting in the API and the MCP server. Contact exports include tags and score, and campaigns can use {{tags}}, {{score}} and {{global.<key>}} too.
    • Merging audiences with Delete the merged audiences afterwards now also moves automation triggers, steps, conditions and exit conditions to the target audience.
    • For the Emailit team (alpha): exit conditions, goals and waits on Placed an order, Abandoned a cart and segment joins and leaves, If/Else rules on segment membership and purchases, and tags and lead score as segment filters.
    • Existing automations keep working as before. In automations built before 2026-10-20, Send email steps aren’t tracked for opens and clicks, and in Contact automations they stay Transactional. Add to audience, Remove from audience, Create contact and Update contact fields steps don’t send webhook events or start other automations, and Remove from audience keeps the contact on the audience as unsubscribed. New steps send events, use the domain’s tracking settings, and Remove from audience deletes the membership.
    • If/Else rules: contains on a list, such as tags, matches whole items; a field that doesn’t exist counts as empty text; number comparisons on an empty value are false; an empty list counts as not set; comma-separated values in is any of are a list; and a group set to any rule without rules is Yes. With Skip the step and continue, a failed step now goes on to the next step (No after an If/Else) instead of ending its branch.
    • Fixed: adding the first step under the trigger of a blank automation opened the trigger instead of the new step.

    See Automation steps and Triggers.

  5. Fixed

    Nested Temple conditionals and {{cf.*}} in automations

    TemplatesAutomations

    • Nested conditionals: Temple now resolves the innermost {{#if}} blocks first, so every {{else}} and {{/if}} belongs to its own block. Nesting works up to 10 levels deep. Before, an inner block closed the outer one early.
    • {{cf.<key>}} in automations: contact automations fill custom fields as {{cf.<key>}} as well as {{custom_fields.<key>}}, so a template written for campaigns works in automations too.

    See Temple and Automation emails.

September 2026

  1. Fixed

    Unsubscribe, automation and contact fixes

    AudiencesAutomationsContacts

    • Unsubscribe links in campaign emails record the opt-out without asking the recipient to sign in.
    • You can save an automation as a draft before every step is configured, for example before you choose a template. Emailit checks the steps when you start the automation.
    • Contact pages with a long email history load without timing out.
    • Audience lists show real subscriber counts, editing a contact no longer changes its audience memberships, and contact exports download correctly.

    See Unsubscribes.

  2. Improved

    Reply-To on automation Send email steps

    Automations

    Set Reply to on a Send email step to send replies to a different address than the template’s, for example a support inbox. If you leave it empty, the step uses the template’s Reply-To.

    See Automation steps.

  3. New

    Template import, export and picker

    TemplatesCampaignsAutomations

    • Import a Dragit .json file, an .html file or a .zip package with images. Images are uploaded to Emailit’s CDN and their links are rewritten.
    • Export a template as Dragit JSON, HTML or ZIP from its menu.
    • Sort the templates list, and use the searchable template picker in campaigns and automations to reach every published template.
    • Save as template on a campaign copies its subject, sender, reply-to address, content and editor into a new template.

    See Import and export templates.

April 2026

  1. New

    Automations (beta)

    Automations

    Start from a template, such as a welcome email, a birthday email, a three-day onboarding sequence or bounce notifications, or build a workflow from scratch. Automations start on contact events, such as a contact joining an audience or a date anniversary, or on email events such as bounced or received, and run steps like Send email, Wait, Condition and Add to audience.

    Each run costs 3 credits, and each email an automation sends or forwards costs 1 credit. See Automations.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.