Why draw it first
Automation tools make it easy to start building at once: drag a box, add an email, connect an arrow. The trouble is that a half-formed idea turns into a half-formed workflow, and the mistakes only show up once real people are receiving real messages.
An automation map is a simple diagram of the flow, drawn on paper, a whiteboard or any plain drawing tool before you touch the software. It forces you to answer questions that building tends to skip. It costs minutes and can save you from an embarrassing send.
What goes on the map
Use only a few shapes. Many people use a rounded box for the start, a rectangle for an action, a diamond for a decision and a small circle for the end. The exact symbols do not matter as long as you use them consistently.
Your map should show:
- The trigger. What event starts this flow, and who exactly can enter it?
- The actions. Each email, tag, task or field change, in order.
- The waits. How long the system pauses between steps.
- The conditions. Every yes/no question that sends contacts down different paths.
- The exits. Every way a person can leave the flow: finishing, buying, unsubscribing, replying, or meeting some other rule.
The building blocks are explained in more detail in the guide to triggers, conditions and actions. If any of those words are new, read that first.
A worked example
Imagine a small online shop planning a post-purchase flow. On paper it might run like this:
- Trigger: an order is marked as shipped.
- Action: send a shipping confirmation straight away.
- Wait: seven days.
- Condition: has the customer opened a support ticket? If yes, exit the flow and let a person follow up. If no, continue.
- Action: send a short message asking how the product is working, with an invitation to reply.
- Wait: fourteen days.
- Action: send a request for a review, with a plain explanation of how it is used.
- Exit: end of flow.
These numbers are illustrations only, not recommendations. Even in this small map, one decision (the support ticket check) shows something easy to miss: without it, an unhappy customer could receive a cheerful review request. Drawing it makes the gap obvious. This sort of work belongs to the post-purchase journey.
Questions to ask while drawing
Walk through the map as if you were the subscriber, and again as the person it could go wrong for.
Entry. Can someone enter twice? If a contact meets the trigger again later, should they restart, be ignored or be held until the first run ends?
Overlap. Could the same person be in two flows at once? A welcome series and a promotion can collide and send several messages in one day. A single master list of flows helps.
Dead ends. Does every path lead somewhere, even if “somewhere” is simply the end? A branch with no destination can silently drop people.
Loops. Can the flow send someone back to an earlier step, such as re-adding a tag that restarts the sequence? Loops that nobody planned can email the same person repeatedly.
Exits. Do customers leave when they buy, unsubscribe or ask for help? A reminder should never reach someone who has already acted.
Missing data. What happens if a field is empty? If an email greets people by first name and the name is blank, the greeting might read badly. Decide on a fallback.
Time. Consider time zones, weekends and holidays. A wait of two days that lands on a Sunday may or may not suit you.
People. Where does a human step in? Mark any point where a staff member should receive a task or take over, a topic that connects to automation limits.
Keep it readable
A map should be understandable at a glance by someone who did not draw it. Keep each flow to one goal. If the diagram sprawls across a page, split it into smaller flows. Label every branch, and write the real condition (“bought in last 30 days”) rather than a vague note (“check customer”).
Add a short key at the top: what the flow is for, who owns it, which list or segment it uses and the date it was drawn. Future you, or a colleague, will be grateful.
From map to build
Once the paper version holds up, build it step by step in your tool, matching the map exactly. Check your platform’s current documentation, since terms and features differ between tools. Then run automation testing with test contacts that follow every branch, not only the main path.
Keep the map afterwards. When you later perform an automation audit, a current diagram makes it far easier to spot what has drifted from the original plan. If you change the workflow, update the map first.
Privacy while you plan
While mapping, note what data each step uses. If a condition relies on tracking or on personal information, check that you have the right to use it; privacy and consent rules vary by country and change, and this is not legal advice. Planning on paper is a good moment to apply data minimisation: if a field is not used by any step, you may not need to collect it.