Every email in a series is a normal Migma email. Each one is fully editable, preflightable, and sendable, the series is just a sequence of them planned together so the story holds across the whole journey.
How it works
Describe the journey you want, including the goal, the audience, and roughly how many emails. Migma plans the arc, then writes and compiles every email in the sequence.Describe the journey
Tell Migma the goal in one prompt, for example a 4-email welcome flow or a 3-part launch sequence.
Migma plans the arc
It decides the role of each email, the order, and how each one hands off to the next, so the sequence reads as one connected story instead of unrelated sends.
Every email is written
Each email is generated and compiled through Migma’s email engine, so the whole sequence is email-safe and built for inbox compatibility.
Refine the whole sequence in chat
Once the series exists, keep shaping it from chat. You don’t edit a static template, you talk to the sequence and it restructures itself.Add an email
Insert a new email anywhere in the journey. Give it a role and a few beats to hit, and Migma writes it to match the rest of the sequence.Remove an email
Drop an email you don’t need. The remaining emails stay intact and renumber their positions.Reorder emails
Change the order of the journey. Pass the new sequence and Migma rearranges the slots.Edit every email at once
The most powerful move is a cross-cutting edit. Ask for one change and Migma applies it to every email in the series at the same time, running each one through the same editing pipeline in parallel. If one email fails, the rest still go through.
One instruction, applied to the entire sequence, consistent voice and styling without touching each email by hand.
Per-email send cadence
For a scheduled journey, each email can carry a send offset, the number of days from the start of the series when it should go out. That’s how you space a drip: day 0, day 2, day 5, and so on.| Role | Send offset | |
|---|---|---|
| 1 | Welcome | Day 0 |
| 2 | Brand story | Day 2 |
| 3 | How to brew | Day 5 |
| 4 | First-order discount | Day 7 |
Restore an email to a previous version
Iterating across a whole series sometimes means a change touches an email you wanted to leave alone. You can restore any email to how it looked on an earlier turn, while leaving the rest of the sequence untouched.Restore works per email, so you can roll back exactly the slots you mean to and keep every other change you’ve made.
Working with individual emails
Each slot on the canvas is a complete Migma email. Click any card to open it in the editor and work on it on its own, then jump back to the canvas to see it in the context of the full journey.Edit one email
Edit one email
Open a slot and refine its copy, images, layout, or colors just like any single email. Changes stay scoped to that email unless you ask for a series-wide edit.
Preflight before sending
Preflight before sending
Run any email in the series through preflight to test it across devices and clients before the journey goes live.
Send the journey
Send the journey
Because each email is a normal Migma email, the whole sequence is ready to schedule and send once you’re happy with it.
What do you want to do next?
Prompt-based creation
Learn how a single prompt turns into a finished, on-brand email.
Write for a persona
Aim the whole sequence at a specific audience so the journey lands.
Preflight before sending
Test every email across 30+ devices before the journey goes out.
The visual canvas
See the whole sequence as connected nodes you can arrange and edit.