What It Does
When you connect a "Go to Workflow" block from one flow to another, the customer execution jumps from the first flow into the second flow. From that point on, the second flow continues as if the customer started there.
How to Set It Up
In your flow, click the Next Step connector from any block
Click the + button on the right
Select Go to Workflow
Choose which flow you want to redirect to from the dropdown
Click Open Flow to view or edit the target flow
When It Works (And When It Doesn't)
Here's the critical part: Go to Workflow only works properly when both flows use compatible triggers.
✅ Works Great With:
Keyword to Keyword Flows
Both flows are triggered by keywords (like "Hi", "Help", "Shop"). When someone jumps from one keyword flow to another, it works smoothly because:
No complex data is needed
Only basic info transfers (name and phone number)
The second flow's trigger gets bypassed since the person is coming from another flow
Example:
Flow 1: Customer says "Hi" →
Ask: "Do you want to talk to an agent or shop products?" →
Customer clicks "Shop Products" →
Go to Workflow: Shop Products Flow
Flow 2: Shop Products Flow (triggered by keyword "shop") →
Flow continues normally even though customer didn't type "shop" →
Shows product catalog that you set up for them
❌ Doesn't Work With:
Keyword to webhook (or vice versa)
If you try to connect a keyword flow to a webhook flow (like Shopify Order Created or Abandoned Checkout), it breaks.
Why?
Webhook flows need specific data that arrives in real time when the webhook fires:
Order number
Product details
Cart URL
Order total
Checkout ID
When someone comes from a keyword flow, none of that data exists. The second flow tries to reference variables like {{trigger.name}} or {{trigger.total_price}}, but they're blank. Messages won't send.
Example of what breaks:
Flow 1: Customer says "Hi" →
Ask: "Want help with your order?" →
Customer clicks "Yes" →
Go to Workflow: Abandoned Checkout Flow ❌
Flow 2: Abandoned Checkout Flow (webhook trigger) →
Tries to send: "Your cart has {{trigger.line_items}} for {{trigger.total_price}}" →
Variables are blank because no webhook fired →
Message fails
The Data Problem Explained
Every trigger brings different data with it.
Keyword Triggers Provide:
Customer name
Customer phone number
Last message content
That's it.
Webhook Triggers Provide:
Everything above PLUS
Order details
Product information
Checkout URLs
Cart contents
Timestamps
Custom fields, etc
When you use "Go to Workflow" to jump into a webhook flow, you bypass the webhook. That means:
✅ The navigation works
❌ But the data doesn't exist
❌ Variables come up blank
❌ Messages don't send
Think of it like trying to read a letter that was never delivered. The mailbox (flow) exists, but there's nothing inside.
When to Use "Go to Workflow"
✅ Good Use Cases:
1. Routing Between Keyword Flows
Main Menu Flow →
Shop Products Flow Main Menu Flow →
Talk to Agent Flow Main Menu Flow →
Track Order Flow
2. Splitting Complex Flows Instead of one massive flow, break it into smaller flows and connect them.
3. Reusing Flows If multiple flows need the same logic at the end, redirect them all to one final flow.
Example:
Flow 1: Instagram Comment Automation →
Customer interested in products →
Go to Workflow: Product Recommendation Flow
Flow 2: WhatsApp Keyword "Shop" →
Customer wants to browse →
Go to Workflow: Product Recommendation Flow
Flow 3: Product Recommendation Flow →
Customer wants be shown products →
Works for both Instagram and WhatsApp customers
❌ Don't Use It For:
1. Jumping into Webhook Flows
Bad: Keyword flow → Abandoned Checkout flow
Bad: Instagram comment flow → Shopify Order Created flow
2. Mixing Incompatible Triggers
Bad: Nitro Product Viewed → Shopify Order Created
Bad: WhatsApp Template sent as part of welcome message → Abandoned Checkout
3. Forcing Data That Doesn't Exist
If the second flow references variables the first flow doesn't have, it won't work.
4. Trying to redirect to a flow that is not of the same channel.
If you have two numbers connected on WhatsApp, you cannot direct an execution from one channel (one number) to a flow that is for another WhatsApp number connected on the same account. Also, this won't work for an Instagram flow where you want to connect at the end of it a WhatsApp flow (because they are different channels).
How to Know If Two Flows Are Compatible
Ask yourself:
Do both flows use the same type of trigger?
Keyword → Keyword ✅
Webhook → Same webhook ✅
Trigger → Same Trigger
Keyword → Webhook ❌
Does the second flow reference variables the first flow doesn't have?
If yes → Won't work ❌
If no → Should work ✅
Can the second flow run with only name and phone number?
If yes → Safe to connect ✅
If no → Don't connect ❌
What Happens When You Connect Flows
Normal Flow Execution:
Customer messages "Hi" →
Keyword trigger fires →
Data arrives: {name: "John", phone: "+1234567890"} →
Flow starts → Messages send
With "Go to Workflow":
Customer messages "Hi" →
Keyword trigger fires in Flow 1 →
Data arrives: {name: "John", phone: "+1234567890"} →
Flow 1 runs → Go to Workflow block redirects to Flow 2 →
Flow 2 trigger gets BYPASSED →
Flow 2 starts with data from Flow 1: {name: "John", phone: "+1234567890"} →
Flow 2 continues
What Breaks:
Customer messages "Hi" →
Keyword trigger fires in Flow 1 →
Data arrives: {name: "John", phone: "+1234567890"} →
Flow 1 runs → Go to Workflow redirects to Abandoned Checkout Flow →
Abandoned Checkout trigger gets BYPASSED →
Abandoned Checkout flow tries to reference {{trigger.cart_url}} ❌ →
Variable is blank because no webhook fired →
Message fails to send
Pro Tips
✅ Always test before launching Trigger the first flow and make sure the second flow runs correctly after the redirect.
✅ Use "Go to Workflow" for routing logic Great for main menu flows that branch into different sub-flows.
✅ Keep webhook flows separate Don't try to force webhook flows to connect with keyword flows.
✅ Document your flow connections If you're connecting multiple flows, add notes so your team knows which flows link to which.
✅ Check variable usage Before connecting flows, make sure the second flow doesn't reference variables that won't exist.
Summary
Go to Workflow works when:
Both flows use compatible triggers (keyword → keyword)
The second flow doesn't need data the first flow doesn't have
You're routing between simple flows
Go to Workflow breaks when:
You try to jump from keyword flows to webhook flows
The second flow references variables that don't exist
You're bypassing a trigger that provides essential data
Bottom line: Always trigger flows as designed so they have the data they need. Structure your automations around trigger types, not around trying to force flows to connect when their data sources don't align.
If you're unsure whether two flows can connect, contact our support team. We'll help you figure out the best way to structure your automation.