Add to Flow Node
The Add to Flow node sends a profile into a different Marketing Automation flow when they reach this point in the current flow. It's how you chain flows together — moving profiles from one journey to the next as part of a larger customer lifecycle.
The profile bypasses the destination flow's Listen node and enters directly, even if they don't match the destination flow's trigger. The profile also stays in the current flow — they continue through any remaining nodes after the Add to Flow node.
In this article
How the Add to Flow node works
When a profile reaches the Add to Flow node, two things happen simultaneously:
The profile enters the destination flow — bypassing its Listen node. They start at the first node after the Listen node in the destination flow, as if they had triggered the Listen node themselves.
The profile continues in the current flow — they don't leave. Any nodes after the Add to Flow node in the current flow are still processed.
This means a profile can be in multiple flows at the same time. They receive messages and go through logic from both flows simultaneously.
⚠️ Important — The profile doesn't leave the current flow
The Add to Flow node adds the profile to another flow — it doesn't move them. If you want the profile to stop receiving messages from the current flow after being added to the destination flow, place an End Flow node immediately after the Add to Flow node.
When to use the Add to Flow node
Use the Add to Flow node when a profile's journey should continue in a different flow — typically because they've reached a transition point in the customer lifecycle. Common reasons:
Lifecycle transitions — welcome → nurture, trial → onboarding, prospect → customer.
Conditional handoffs — a profile didn't respond to nurture emails → move them to a re-engagement flow.
Modular flow design — keep flows focused on one stage, then chain them together. Easier to maintain than one massive flow.
Reusable destination flows — a single "Win-back" flow can receive profiles from multiple source flows.
Common use cases
Welcome → Nurture handoff
Welcome flow: Listen (form submit) → Email (welcome) → Time (3 days) → Email (getting started) → Add to Flow (Nurture flow) → End Flow. The profile enters the nurture flow automatically after completing the welcome series.
Non-responder → Re-engagement
Nurture flow: Email → Wait for Event (click, 5 days) → No path: Add to Flow (Re-engagement flow) → End Flow. Profiles who didn't engage are routed to a dedicated re-engagement journey.
Trial expired → Win-back
Trial onboarding flow: Wait for Event (custom event: "subscription_started", 14 days) → No path (trial expired without converting): Add to Flow (Win-back flow) → End Flow. Profiles who didn't convert during the trial are moved to a win-back journey.
Lead qualified → Sales handoff flow
Nurture flow: Achievement node (MQL) → Notification (alert sales) → Add to Flow (Sales-ready nurture flow) → End Flow. The profile transitions to a sales-focused flow with different content and cadence.
Post-purchase → Loyalty flow
Post-purchase flow: Email (thank you) → Time (7 days) → Email (review request) → Add to Flow (Loyalty program flow) → End Flow. First-time buyers are automatically enrolled in the loyalty program journey.
Setting up the Add to Flow node
Drag the Add to Flow node onto the canvas and click it to open the configuration panel.
Select the destination flow from the dropdown. All active and paused flows in your account are listed. Use the search box if you have a lot of flows.
Preview the destination flow by hovering over it in the list. This gives you a quick overview of the flow's structure without leaving the current canvas.
Decide what comes next in the current flow. You have two options:
End the current flow: Connect an End Flow node after the Add to Flow node. The profile's journey in the current flow ends; they continue only in the destination flow.
Continue the current flow: Connect more nodes after the Add to Flow node. The profile is now in both flows simultaneously and will receive messages from both.
💡 Tip — In most cases, end the current flow
Unless you specifically need the profile to continue in both flows simultaneously, place an End Flow node right after the Add to Flow node. This creates a clean handoff and prevents accidental over-communication.
Entry Limit interaction (in Flow settings)
The destination flow's Entry Limit still applies when profiles are added via the Add to Flow node. If the destination flow's Entry Limit is set to 1 and the profile has already entered that flow before (through any entry method), the Add to Flow node will not add them again.
Destination flow Entry Limit | What happens |
Entry Limit = 1 (profile already entered before) | Profile is not added to the destination flow. They continue in the current flow as normal — but the handoff doesn't happen. |
Entry Limit = 1 (profile has never entered) | Profile enters the destination flow successfully. |
Entry Limit > 1 or unlimited | Profile enters the destination flow (as long as they haven't exceeded the limit). |
⚠️ Important — Silent failure
If the profile can't enter the destination flow because of the Entry Limit, there is no error or notification — the node is simply bypassed for that profile. They continue in the current flow as if the Add to Flow node was skipped.
If this is a critical handoff point, consider using the Check Profile node before the Add to Flow to verify the profile hasn't already been through the destination flow (e.g. check for a tag or achievement set at the end of that flow).
Avoiding over-communication
When a profile is in multiple flows simultaneously, they can receive messages from all of them. This is the biggest risk when using the Add to Flow node — and the most common mistake.
Example of the problem
Flow A sends a nurture email on Tuesday. Flow B (which the profile just entered via Add to Flow) sends an onboarding email on the same Tuesday. The profile receives two automated emails on the same day from the same brand — which may feel like spam.
How to prevent it
Strategy | How |
End the source flow | Place an End Flow node after the Add to Flow node. The profile only receives messages from the destination flow going forward. |
Use Termination Tags | In the destination flow, use an Update Profile node to add a tag. Set that tag as a Termination Tag in the source flow. When the profile enters the destination flow, they're automatically removed from the source flow. |
Add Time nodes for spacing | If the profile must be in both flows, make sure neither flow sends a message immediately. Use Time nodes to space messages across flows. |
Think through the full journey | Before activating, map out what messages the profile could receive from all active flows on any given day. If the total exceeds what's reasonable (1–2 messages/day max for most brands), adjust the timing or remove overlap. |
Add to Flow vs. Achievement as a flow trigger
There are two ways to move a profile from one flow to another. Here's when to use each:
Method | How it works | Best for |
Add to Flow node | Directly injects the profile into the destination flow. The source flow explicitly controls the handoff. Tight coupling between flows. | Clear, linear handoffs where the source flow always sends the profile to the same destination. Simple to set up. One source → one destination. |
Achievement as trigger | The source flow assigns an achievement. A separate flow's Listen node listens for that achievement event and triggers independently. Loose coupling. | Multiple source flows that should all trigger the same next journey. Or when you want the destination flow to be independent and maintainable on its own. Many sources → one destination. |
💡 Rule of thumb
One source flow → one specific destination →Add to Flow node(simpler).
Multiple source flows → same next journey →Achievement as trigger(more flexible, flows stay independent).
Keeping track of connected flows
As you chain flows together, it can become difficult to remember which flows feed into which. Here are strategies to keep things manageable:
Tag profiles with their source flow. Before the Add to Flow node, add an Update Profile node that tags the profile with the source flow name — for example, MA: Source = Welcome flow. In the destination flow, you can use this tag to track where profiles came from.
Use the Goals feature. In each flow's bottom bar, use the Goals section to document which flows connect to this one (both inbound and outbound). For example: "Receives profiles from: Welcome flow, Trial flow. Sends profiles to: Sales nurture flow."
Maintain a flow map. For complex setups with many interconnected flows, keep a simple diagram (even a spreadsheet) documenting all flows and their connections. Update it whenever you create or modify a flow chain.
Use consistent naming. Name flows in a way that makes the lifecycle stage clear — for example: "01 - Welcome", "02 - Nurture", "03 - Re-engagement", "04 - Win-back". Numbered prefixes make the sequence visible in the flow list.
Troubleshooting
Issue | What to check |
Profile not appearing in the destination flow | Check the destination flow's Entry Limit. If set to 1 and the profile has already entered, the handoff is silently skipped. Also check that the destination flow is Active (not Draft or Stopped). A Paused destination flow will accept profiles but hold them at the Listen node. |
Profile receiving messages from both flows | The profile is in both flows simultaneously. Place an End Flow node after the Add to Flow node in the source flow, or use a Termination Tag to remove the profile from the source flow when they enter the destination. |
Destination flow not listed in the dropdown | Only Active and Paused flows appear in the selector. If the destination flow is in Draft status, it won't be listed. Activate or pause the destination flow first. |
Profile stuck or not progressing in destination flow | The Add to Flow node bypasses the Listen node but the profile still needs to meet other requirements — such as Subscription requirements on Email/SMS nodes in the destination flow. Also check for unconfigured nodes in the destination flow. |
Can't tell which profiles came from which source | Add an Update Profile node before the Add to Flow node to tag profiles with the source flow name. See Keeping track of connected flows. |
Tips & best practices
End the source flow after the handoff — unless you have a reason not to. In most cases, you want a clean transition. Profile enters destination flow, source flow ends. Over-communication is the biggest risk of leaving both flows active.
Check the destination flow's Entry Limit. If it's set to 1, profiles who've already been through it won't enter again. Consider setting it to unlimited if the destination flow is designed to receive profiles repeatedly (e.g. a recurring re-engagement flow).
Tag before you hand off. Use an Update Profile node to add a source tag before the Add to Flow node. This makes it easy to track and segment profiles by their journey path.
Use Termination Tags for cross-flow coordination. If the destination flow represents a conversion (e.g. purchase), have it apply a Termination Tag that removes the profile from prospecting or nurture flows. See Update Profile Node → Termination Tag pattern.
Keep flows focused. Instead of one massive flow with 50 nodes, build smaller flows for each lifecycle stage and chain them with Add to Flow nodes. Each flow is easier to understand, test, and maintain.
Document your flow connections. Use the Goals feature and consider maintaining a simple flow map. As your automation setup grows, undocumented connections become a maintenance headache.
Test the full chain. Before activating, send a test profile through the source flow and verify they appear in the destination flow. Check the Node Stats on both flows to confirm the handoff worked.
Consider Achievement triggers for complex networks. If more than 2–3 source flows feed into the same destination, switch to an Achievement-based trigger instead of multiple Add to Flow nodes. It's cleaner and keeps flows independent.
Related articles
Marketing Automation Nodes — Overview of every node type.
End Flow Node — End the source flow cleanly after a handoff.
Update Profile Node — Tag profiles with source flow and apply Termination Tags.
Achievement Node — Alternative flow-chaining method via achievement events.
Listen Node — The entry point that Add to Flow bypasses in the destination flow.
Time Node — Spacing messages to avoid over-communication across flows.
Navigate the Canvas — Goals feature and Flow Settings.
Key Terms Glossary — Definitions for all Marketing Automation terms.