What we do
Tools
Industries
Department
How we workLet's talk →
Home/Mailchimp/Mailchimp Email Automation by Plan and Trigger
Mailchimp

Mailchimp Email Automation: What Your Plan Can Build, and What Starts It

Mailchimp now calls its automations flows. The older Customer Journey builder and classic automations live on inside them, and old classic ones can be converted. What you can build depends a lot on your plan, and whether a flow ever sends depends on its starting point. Both are below.

What each plan gets

Free: a preview of flows only. You can't send email from a flow on Free.

Essentials: flows of up to 4 steps, one starting point, no branching. Enough for a short welcome series or a single cart reminder.

Standard and Premium: much longer flows, multiple starting points, and branching points that send contacts down different paths.

Where to find them: the Automations menu, then the All flows page. Pre-built flows (welcome, abandoned cart, birthday, first purchase) are the fastest start.

Automations All flows

Flow switched on, nothing sent

Your contacts qualified before the flow went live

How you'll know: The audience is full of people who match, and the flow report shows nobody entered.

Fix: Flows react to the trigger happening after they're on. To include existing contacts, make the trigger happen again for them, for example by applying the starting tag to a segment of them in bulk.

It's still a draft, or it's paused

How you'll know: Edits look saved, but the flow status isn't active.

Fix: Review the flow and turn it on. A flow paused to fix one email stays paused until someone resumes it.

The step limit cut it short

How you'll know: On Essentials, your five-email series only ever sends four.

Fix: Essentials caps a flow at 4 steps. Shorten the series, split it into two flows chained by a tag, or move to Standard.

The event name is off by a character

How you'll know: Your system posts events, they appear on the contact's activity, and the flow ignores them.

Fix: The Event API starting point matches one event name exactly. invoice_paid and Invoice Paid are different events. Fix the sender or the flow so they agree.

The contact is unsubscribed or cleaned

How you'll know: One person never gets the emails while others do.

Fix: Flows only email subscribed contacts. Check their status in the audience before debugging the flow.

Pick the starting point that matches what actually happens

Most flows that misfire were started on the nearest trigger Mailchimp had, not the event the business cares about.

What you want to react to Starting point Catch
Someone joins your list or signs up through a Mailchimp form A signup or joins-audience starting point. The standard welcome series. People added by import may not count as new signups. Check how they arrived before expecting a welcome email.
A purchase or abandoned cart on Shopify, WooCommerce or another connected store The purchase and cart starting points, fed by the store connection. Only works for orders that come through the connected store. Phone, wholesale and in-person sales never show up.
A birthday or anniversary A date-based starting point reading a date field on the contact. The field has to be filled in and in the right format, or the flow quietly skips that contact.
A tag you apply A tag-added starting point. Fine when a system applies the tag. When a person has to remember, the flow runs as often as they do.
Something in another system: a renewal, a paid invoice, a closed ticket, a finished job The Event API starting point, under API & Integrations. Available from Essentials up. Mailchimp only listens. Something outside it has to post the event to the contact, with the exact event name the flow expects.

When the trigger lives outside Mailchimp

A classic automation was one trigger and a straight line of sends. A flow can branch: on Standard and up, a first-time buyer and a repeat customer can take different paths in the same flow, based on tags, opens or store data. That covers most marketing jobs without any outside help.

The gap is the event Mailchimp never sees. A membership renews in your billing tool. A service job closes in your field software. An invoice gets paid in QuickBooks. Mailchimp can start a flow from any of those through the Event API, but only if something posts the event to the right contact when it happens, and branching on account tier or loyalty status only works if those fields are kept current on the contact.

n-frames builds that piece: a sender in your CRM, billing or order system that posts the event the moment it happens, keeps the fields your branches read up to date, and alerts someone if posting fails. Our Mailchimp integrations page covers which systems already have a connector, and the Mailchimp API key guide covers the credentials side.

Questions people ask

What is the difference between a Mailchimp automation and a Customer Journey?

A classic automation ran one straight sequence from one trigger. A Customer Journey, now built as a flow, can branch into different paths based on behavior, tags or purchase data, and on Standard and up it can have more than one starting point. Mailchimp lets you convert an old classic automation into a flow.

Can Mailchimp send a welcome email or birthday email automatically?

Yes. Both are pre-built flows. A welcome series starts on a new signup, and a birthday email reads a date field on the contact, so it only works for contacts who have that field filled in.

What is an autoresponder in Mailchimp?

The old name for a simple automated email or sequence sent after a trigger, such as a thank-you after someone signs up. Mailchimp now builds the same thing as a flow, so you won't find a separate autoresponder tool.

Can a Mailchimp automation trigger off something outside Mailchimp?

Yes, through the Event API starting point, but Mailchimp doesn't go looking for the event. Your CRM, billing system or support desk has to post it to the contact through the API, or through a tool like Zapier, with the exact event name the flow expects. n-frames builds and monitors that sender when no ready-made connector covers your system.

Why isn't my Mailchimp automation enrolling contacts who already existed before I turned it on?

Because a flow only reacts to its trigger happening after it's active. Contacts who already matched aren't enrolled after the fact. Re-create the trigger for them, such as tagging that group in bulk, or send them a one-off campaign instead.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.