Email Automation Examples: 12 Flows to Build With Triggers and Timing

Most people understand email automation in theory: set it up once and it sends the right message at the right moment. The hard part is knowing which automations to build first and what they should actually say. This guide walks through twelve email automations that work for ecommerce, SaaS, education and service businesses, with the trigger, timing, content idea and goal for each, plus a plan for building them in order, how to measure them and the mistakes that make automations annoying. It pairs with our broader guides to marketing automation and drip campaigns.

What counts as an email automation?

An email automation is a message, or a short series of messages, that sends itself when a condition is met: a person signs up, buys, abandons a cart, goes quiet or hits a date. The condition is the trigger, the delay is the wait and the check that stops the flow once the goal is met is the exit. The idea comes from the wider field of marketing automation. Because the messages respond to behaviour, they tend to feel more relevant than a campaign sent to everyone at once.

Twelve email automations to build

You do not need all twelve at the start. The first four or five usually give the most return. Most of the rest are refinements.

What each one should say

Welcome series

Send the first message within minutes. Say thank you, deliver anything promised, explain what to expect and give one clear next step. Follow with one or two emails over the next days that show your best content or products. See welcome email series.

Abandoned cart

Show the items left behind with images, answer likely doubts (delivery time, returns, payment options) and make returning one click. Only add a discount in a later email, and only if margins allow. Read abandoned cart recovery.

Browse abandonment

Softer than the cart reminder. Show the products they looked at and a few similar ones, and avoid implying you are watching them. Use only data you have consent to use, as covered in our DPDP Act guide.

Post-purchase and review request

Start with usage help, not a request. Once the product has had time to prove itself, ask for feedback with a one-tap rating. See user-generated content and customer feedback loops.

Replenishment

For products that run out, such as coffee or skincare, use the average gap between orders to time a gentle reminder with an easy reorder button.

Win-back

Acknowledge the gap, offer something genuinely useful and make leaving easy. If there is no response after a short sequence, stop sending. See win-back campaigns.

How to build your automation programme

1. Pick the first flows by value. Usually welcome, abandoned cart and post-purchase for stores, welcome and onboarding for software.
2. Define the trigger and exit. Exactly what starts it and what ends it. A cart flow should stop when the order is placed.
3. Write the whole sequence. Plan every email, wait and branch before building.
4. Add conditions. Skip people who already did the action, or who recently received a message.
5. Set frequency limits. Cap how many automated and campaign emails one person can receive per week.
6. Test end to end. Use a test profile to walk through every branch and check links, personalization and timing.
7. Launch to a small share first. Watch metrics and spam complaints, then roll out.
8. Review monthly. Look at each step’s performance and improve the weakest.

In Flowfox, these are built in the journey builder with triggers from your event data, waits, branches and goals, and the messages are designed in the email builder. Sector examples are on the ecommerce, SaaS and edtech pages, and the onboarding and retention use cases show full flows.

Journey: Abandoned cart
Trigger:  event cart_updated with items > 0
Wait:     2 hours
Check:    has event order_placed since trigger?  -> yes: exit
Send:     Email "You left something behind"
Wait:     1 day
Check:    has event order_placed since trigger?  -> yes: exit
Send:     Email "Still thinking it over?" (answers to common questions)
Goal:     order_placed

A worked example (invented)

A small online tea shop sends a monthly newsletter and nothing else. Over three months, it adds a three-email welcome series, a two-email cart recovery and a replenishment reminder for loose-leaf teas, timed at 28 days after purchase. After the first quarter, the owner finds that the automated flows produce a larger share of email revenue than the newsletter, with a fraction of the weekly effort. The welcome series also reduces early unsubscribes because new subscribers know what to expect. Then comes a mistake: the replenishment email was sent to customers who had bought a gift set, who do not reorder tea for themselves. The fix is a condition that only sends it to customers who bought a single-variety pouch. The shop and numbers are invented, but the lesson is real: a good automation needs the right condition as much as the right copy.

How to measure automations

Use a small holdout group, say 5 to 10 percent, that does not receive the flow so that you can see what would have happened anyway. Without one, you may credit the automation with sales that were coming regardless. For the wider discipline, see email marketing. Read holdout testing for the principle, and our guide to A/B testing for how to compare variants.

Common mistakes

• No exit condition. People keep getting a cart reminder after they have bought.
• Stacking flows. A customer can land in four automations at once without frequency rules.
• Set and forget. Offers, prices and links go stale.
• Ignoring consent. Use only data and channels people agreed to.
• Everything on email. Some moments suit WhatsApp or SMS. See email vs SMS vs WhatsApp.

The best automation feels like attention, not automation. It arrives when you need it and stops when you have done what it asked.

Read next: welcome email series, WhatsApp commerce and the blog.