Email Automation Examples: 15 Workflows Worth Copying

Email automation examples are easiest to understand as a set of small, single-purpose workflows: a trigger that starts them, a wait that spaces the steps, and a condition that decides who continues. Below are fifteen you can copy, grouped by the job they do — capturing new contacts, converting interest into a purchase, keeping customers engaged, and keeping your own team informed. Each one lists the trigger, the timing, the email outline, and why it works.

What separates a good automation from a forgettable one

Every workflow that earns its place has three parts. The trigger is the event that starts it: a signup, a product event, a date, a stretch of inactivity, or a website action like viewing a pricing page. The wait is how long the workflow pauses before the next step — hours, days, or until a specific weekday morning. The condition is the branch that changes the path: did they click, did they buy, did they log in?

Good automations are short, do one thing, and stop when the goal is met. That last part is what most first attempts get wrong. A welcome sequence that keeps sending after someone has already upgraded isn't nurturing — it's noise.

If you're building in Mailerflow, these examples map directly onto its visual automations, which support waits, conditions, webhooks and AI steps, with triggers on signups, events, dates, inactivity and website behavior. If you're using another tool, check which trigger types it supports before you plan the workflow — the examples below note where a trigger is doing heavy lifting.

Choosing a provider at the same time? Our comparison of the Best Email Marketing Platforms ranks them by verified prices for your list size and sending volume.

Examples for capturing and welcoming new contacts

1. The single-email welcome with one job

Trigger: signup form submitted. Timing: immediately.

Outline: Subject line that repeats the promise they signed up for. Body: deliver the thing (link or file), one sentence on what to expect from you and how often, one next step.

Why it works: it sets expectations and earns the second open. If you use double opt-in, this first email is the confirmation — keep it to a single button and nothing else competing for the click.

2. The three-email onboarding sequence

Trigger: signup. Timing: day 0, day 2, day 5.

Outline: Email 1 is orientation — where things are, what to do first. Email 2 covers the one feature most people miss, with a screenshot or short walkthrough. Email 3 asks them to complete a small win in five minutes.

Why it works: each email has a distinct job instead of repeating the same pitch. Three is a common stopping point; if you can't name what email four would teach, stop at three.

3. The lead magnet follow-up that segments on click

Trigger: signup tagged with the specific download. Timing: immediate, then a branch after 24 hours.

Outline: Deliver the asset. Then split on whether they clicked the "advanced" link inside it. Advanced readers get the deeper sequence; everyone else gets the basics.

Why it works: the click is a real signal, not a guess. It's also a very low-effort segmentation to build — one link, one condition.

4. The no-show follow-up

Trigger: event registration where the attendance field stays empty. Timing: two hours after the event ends.

Outline: Acknowledge the miss without guilt ("you probably had a conflict"), offer the recording, offer the next date.

Why it works: it recovers intent that would otherwise go cold. The person already raised their hand once; a no-show isn't a rejection.

Examples for turning interest into a purchase

This is the group where timing and conditions matter most. A reminder that arrives too late reads as a generic promotion; the same message four hours after a product view tends to read as helpful.

5. The browse-abandon nudge

Trigger: website behavior — a product page viewed without a purchase. Timing: four to six hours later.

Outline: Show the product again, give one concrete reason people choose it, link back to the page.

Why it works: it arrives while the interest is still warm. This needs website-behavior tracking; Mailerflow's JS SDK feeds that kind of trigger, and other platforms handle it through their own tracking script or a connected analytics tool.

6. The cart-abandon sequence with a condition

Trigger: cart created, no order event. Timing: one hour, then 24 hours.

Outline: Email 1 is a plain reminder with the cart contents and a link back. Email 2 answers the most common objection — shipping, returns, sizing, whatever your support inbox says most.

Why it works: the second email only sends if the first didn't convert. That's a condition, not a fixed drip, and it's the difference between a sequence that respects the customer and one that nags.

7. The trial-ending reminder

Trigger: date-based, three days before trial end. Timing: day −3 and day −1.

Outline: Summarize what they've built or set up so far, state plainly what happens at expiry, and give a one-click path to keep it.

Why it works: it removes the surprise that causes churn. Trial cancellations are often passive — the card simply isn't added.

8. The win-back for a lapsed trial

Trigger: inactivity — no login for 14 days after trial expiry. Timing: day 14, then day 30.

Outline: What's changed since they left, framed around their original use case, plus a short path back in.

Why it works: it targets a specific reason for silence rather than blasting the whole list. Two emails is often enough; add a third only if you have something new to say.

Examples for keeping customers engaged

Retention automations are the ones most people skip, which is exactly why they're worth building. They're also the easiest to justify, because the audience is already paying you.

9. The activation check-in

Trigger: signup, with a condition of no key event within seven days. Timing: day 7.

Outline: Ask directly what's blocking them, and link to the fastest path to first value.

Why it works: it catches people before they quietly give up. Replies to this email can be some of the most useful feedback you get.

10. The feature-adoption drip

Trigger: event — first use of feature A. Timing: three days later.

Outline: Introduce feature B, which pairs naturally with A, and show the two working together.

Why it works: it sequences education by what the customer already did. Someone who just connected an integration is a very different reader from someone who hasn't logged in.

11. The milestone or anniversary email

Trigger: date-based — one year since first purchase. Timing: on the date.

Outline: Acknowledge the milestone, then offer something relevant to their history — an upgrade path, a loyalty perk, or early access.

Why it works: it's a genuine reason to write, not a manufactured one. Keep it short and skip the confetti graphics.

12. The re-engagement sequence before you suppress

Trigger: inactivity — no opens or clicks for 90 days. Timing: day 90 and day 104.

Outline: Email 1 asks "still want to hear from us?" with a single confirmation link. Email 2 is a clear last chance, and says what happens if they don't respond.

Why it works: it protects deliverability by giving people an easy exit. Mailerflow automatically suppresses bounces and complaints; a re-engagement flow is the manual counterpart for people who are still reachable but no longer interested. For more on how this differs from a fixed drip, see drip campaigns vs triggered emails.

Examples for internal and operational workflows

These aren't marketing emails. They're the ones that save your team time and keep your data honest.

13. The new-signup alert to your team

Trigger: signup. Timing: immediate.

Outline: An internal notification with the contact's source, plan and any custom field that matters — company size, use case, referral code.

Why it works: sales or support can act while the person is still on the site. This can be a webhook step rather than an email, which keeps it out of your sending reputation entirely.

14. The high-value-action alert

Trigger: event — a contact crosses a usage or spend threshold. Timing: immediate.

Outline: Internal alert with the trigger detail and a direct link to the contact record.

Why it works: it turns product activity into a timely human touch. The threshold is the whole design: pick a number that means "worth a phone call," not "worth a glance."

15. The data-sync webhook

Trigger: tag added or field changed. Timing: immediate.

Outline: No email at all — a signed webhook to your CRM or data warehouse.

Why it works: it keeps systems consistent without manual exports. Mailerflow's signed real-time webhooks include retries and delivery logs, and webhooks are a step type inside visual automations, so the same workflow can notify your team and update your CRM.

The patterns behind all fifteen

Strip away the specifics and you'll find five reusable patterns. Apply them to any workflow that isn't on this list.

1. Deliver, then ask. The first email gives something (the asset, the recording, the answer). The second asks for something (a click, a reply, a purchase). Reversing the order is a common reason a sequence underperforms.
2. Branch on a real signal. A click, a login, a purchase, a page view. If your branch is based on something you assumed rather than something the contact did, it's a guess dressed up as personalization.
3. Wait for the goal, then stop. Every workflow needs an exit condition. "Purchased" should remove someone from the cart sequence, the browse nudge, and the trial reminder.
4. One email, one job. If you can't summarize an email's purpose in a sentence, split it into two or cut it.
5. Exit on conversion. Related to the third, but worth stating separately: the moment someone does the thing you wanted, the automation should go quiet. Nothing erodes trust faster than a discount code arriving after full-price checkout.

If you'd rather start from a pre-built structure, there's a library of ready-made automation templates that follows these same patterns.

How to build your own, step by step

1. Pick one goal and one trigger. "Get trial users to their first key action" is a goal. "Send more email" is not.
2. Write the exit condition first. Before you draft a single email, decide what makes someone leave the workflow. This one habit prevents many automation mistakes.
3. Draft the emails. Keep each to one job, one primary link, and a subject line you'd actually open.
4. Add waits and conditions. Space the steps by days, not hours, unless the trigger is time-sensitive like a cart or a no-show.
5. Test with a real address. Send yourself through the whole path, including the branches. Check the mobile rendering while you're there.
6. Check the send window. If you use "send when the contact is most active," confirm it behaves as you expect across time zones.
7. Activate, then review after two weeks. Look at where people drop out and where they exit. Adjust one thing at a time.

If you want a head start on steps 1 through 4, Mailerflow's AI automation builder lets you describe a workflow in a sentence and it drafts the trigger, waits, conditions and emails for you to review before activation. It's useful for a first draft, but it won't know your exit condition — that part is still yours. The AI email builder can take the copy and design step from a description to a complete responsive email with subject lines and preview text. You can see how the pieces fit together on the automation overview page.

Mistakes that quietly break automations

• No exit condition. People keep getting emails after they've already converted. Fix: add a condition at the top of every workflow that checks the goal state.
• Too many emails too fast. Three emails in 24 hours can feel like pressure. Fix: space steps by at least a day unless the trigger is genuinely urgent.
• Sending to the whole list instead of a segment. A win-back sent to active customers is confusing. Fix: scope every workflow to a dynamic segment.
• No suppression of recent buyers. Nothing says "we're not paying attention" like a first-purchase discount after a purchase. Fix: exclude buyers from acquisition flows for a set period.
• Forgetting time zones and send windows. A 3 a.m. delivery is likely to get buried. Fix: set a send window and let the platform handle local timing.
• Never reviewing performance. An automation you set up a year ago may be pointing at a page that no longer exists. Fix: put a quarterly review on the calendar.

FAQ

How many automations should a small list have?

Start with two: a welcome sequence and one conversion workflow (cart, trial, or browse abandon, whichever matches your business). Add a re-engagement flow once your list is large enough that inactivity is a real segment. If you have more than five active workflows on a small list, you may be optimizing before you have data.

What's the difference between an automation and a campaign?

A campaign is a one-time send to a segment. An automation is a workflow that runs continuously, triggered by behavior, dates, or events, and each contact moves through it on their own timeline. Most programs need both: campaigns for announcements, automations for everything that should happen without you.

Do automated emails hurt deliverability?

Not inherently. Deliverability depends on engagement, authentication, and complaint rates, not on whether a send was triggered or scheduled. The risk with automations is sending too often to people who aren't engaging, which is why exit conditions and re-engagement flows matter. Setting up DKIM, SPF and DMARC on your own domain is the other half of the picture.

How long should a welcome sequence be?

Three to five emails over one to two weeks is a common starting point. The right length is however many emails you can write that each teach or offer something distinct. If email four repeats email two, you've found your stopping point.

Can I automate emails based on website behavior?

Yes, if your platform tracks page views and passes them to the automation engine. Typical triggers are a product page viewed without a purchase, a pricing page viewed more than once, or a specific page visited after a campaign click. Check your platform's tracking setup before you design the workflow, since this trigger type usually requires a script on your site.

Describe this automation in a sentence and Mailerflow drafts the workflow for you to review — start free.