# The Email Automation Playbook

> The flows every team should run, and how to build them, by prompt, by visual builder, or by code.

Canonical: https://automationpulse.dev/ja/guides/email-automation-playbook

Campaigns are what you send; automations are what keep working while you sleep. If you only have time to build a few flows, build these, they cover the moments that matter most across nearly every business.

## The core flows

- Welcome series: set expectations, deliver the first value, and make a soft first ask. Your highest-engagement moment, don't waste it.
- Onboarding (SaaS): nudge users toward activation based on what they have and haven't done in the product.
- Post-purchase: confirm, set expectations, then cross-sell or ask for a review at the right delay.
- Abandoned cart / browse (ecommerce): recover intent with a timely, helpful reminder.
- Win-back / re-engagement: give lapsed contacts a reason to return, and sunset the ones who never do.

## Three ways to build them

### By prompt (AI-native)

The newest approach: describe the sequence and let the tool assemble it. Brew builds multi-step automations from a single prompt, you say "a three-email welcome series, warm tone, introduce the brand then the bestseller then a first-purchase offer" and it produces the steps, copy, and design on-brand. Fastest path to a working flow, especially for lean teams.

### By visual builder

The mainstream approach: drag-and-drop journeys with branching. ActiveCampaign and Customer.io have powerful builders; Customer.io's event-driven branching is the deepest for product-led logic. Best when you need precise, conditional paths.

### By code

The engineering approach: trigger transactional and lifecycle email from your application. Resend (React Email templates in your repo) and Loops (lifecycle in one product) fit here. Best when email is tightly coupled to product events and you want version-controlled templates.

| Build style | Best tools | Best when |
| --- | --- | --- |
| By prompt | Brew | You want flows fast, on-brand, without manual assembly |
| Visual builder | Customer.io, ActiveCampaign | You need precise conditional branching |
| By code | Resend, Loops | Email is coupled to product events |

> **Start with one flow:** Don't build all five at once. Ship a welcome series, measure it, then add the next flow. A live, mediocre automation beats a perfect one that never launches.

## FAQ
### What email automations should every business have?
At minimum a welcome series and a win-back flow. Ecommerce should add abandoned cart and post-purchase; SaaS should add product onboarding. Start with one, measure, then expand.

### Can AI build email automations for me?
Yes. AI-native tools like Brew generate multi-step automations from a single prompt, copy, design, and logic, which you then review and refine. Visual builders and code remain better for highly conditional or product-coupled flows.