Marketing Automation Flows: What They Are and Why Yours Stays Quiet
A look at how marketing automation flows route your contacts, the plan gates and SMS approval rules behind them, and where to build one.
Small businesses that market to the customer lists they keep beside their QuickBooks books keep hitting the same wall. They build a marketing automation flow, switch it on, and then wait for messages that never arrive. The accepted answer on the subject is an overview published by Intuit, the vendor behind the marketing platform. It explains the mechanics well. We have summarized it here and added the practical steps it leaves out.
What is a marketing automation flow?
A flow is an automated route through your marketing. Each contact walks a path shaped by their own behavior: what they open, what they click, what they join. You assemble that route from triggers, rules, and actions. The system then moves each contact along it without further prompting from you.
The visual version of the route is the flow map. It shows every path a contact could take, branch by branch, before anything sends. Two contacts can enter the same flow and finish with completely different experiences. That is the entire point: personalization at a scale no one could manage by hand.
Where do you build a flow?
Sign in to your Intuit marketing account first. In current accounts, the builder sits in the Automations area of the main menu. Open customer journeys there, then create a new flow from a blank map or a preset template. Labels shift a little between plans, so expect small wording differences.
The builder opens on the map itself. You place a starting trigger at the top, then add rules and actions beneath it. Nothing runs until you activate the flow with its own switch. That last step matters more than people expect, and the next section explains why.
Why do triggers ignore past activity?
This is the trap that catches almost everyone. Triggers respond only to events that happen after a flow goes live. A contact who signed up on Monday will not enter a flow you activated on Tuesday. The trigger has no memory of earlier behavior.
Plan for that gap when you launch. Segment the older contacts inside your audience first, then use whatever manual entry option your plan provides to bring them in. Some tiers allow adding existing contacts to a running flow by hand. Test before you rely on any of it. Activate the flow, perform the trigger action yourself with a seed address, and confirm the contact lands on the map.
The parts of a flow, in plain terms
The vocabulary is compact. A trigger is the event that adds a contact: a signup, a purchase, a form submission. A step is anything that follows a trigger. A rule decides how and when a contact proceeds down a path, such as a one week wait or a branch on behavior. An action is the task the system performs when a contact arrives: send an email, send a text, or apply a tag. An exit condition removes a contact from the flow entirely.
A simple welcome sequence shows the pieces working together. The trigger is a signup. The rule waits one week. The action sends the message. The exit condition pulls out anyone who bought during the wait, so buyers get order messaging instead of a nudge.
Plan gates and the SMS approval requirement
Two gates stand in front of these tools. The first is your subscription. The vendor’s overview states plainly that flow features vary by plan, so a missing option usually reflects your tier rather than a fault. Review what your plan includes in your billing settings before assuming a bug.
The second gate concerns text messaging. Any flow built around SMS requires an approved SMS marketing program at the account level. Approval is reviewed, not instant, and text steps stall until the program clears. To see where yours stands, look for the SMS marketing area in your account settings. The wording varies, but the program status shows there. Wait for approval before wiring texts into anything time sensitive.
Flows are not classic automations
Longtime users arrive confused because two systems coexist. Classic automations, the older email tool, still run in plenty of accounts. Flows are the newer, branch-heavy system, and the two do not merge. A contact in a classic automation never appears on your flow map, and settings do not carry across.
Pick one system per purpose. A simple classic automation, meaning a trigger, a delay, and a send, converts to a flow with little effort. Anything with heavy branching deserves a rebuild from scratch, where the map shows every path.
A silent flow usually has one of five causes
When nothing sends, run the checks in order. Confirm the flow is active, not merely saved. Confirm the triggering event happened after activation. Confirm the features you used exist in your plan. Confirm any SMS program is approved. Then inspect the exit conditions, because a broad one can remove contacts almost as fast as they enter. Test the whole chain with your own address before judging the result. Almost every silent flow traces back to one of those five points rather than to a defect.