The Problem
You might think you can link a webhook triggered flow from another flow (like connecting it as the next step in a welcome flow). While technically possible, this creates a critical data issue.
How Webhook Flows Work
Webhook triggered flows receive a payload of data when activated.
Example: Say you want to manually trigger an abandoned checkout flow from a keyword flow. You connect the webhook flow at the end of the keyword flow. The problem? The abandoned checkout flow needs specific data that arrives in real time through the webhook:
Customer name
Contact phone
Email
Tags
Which product was abandoned
Other checkout details
The keyword flow doesnt have this data. So even if the trigger gets bypassed and the flow starts, it cant reference data that doesnt exist. The messages wont send.
What Happens When You Link Flows
When you jump from one flow directly into a webhook triggered flow:
✅ The navigation works
❌ But the data doesnt exist
Why It Breaks
When you bypass the webhook trigger:
No webhook fires
No payload arrives
The flow tries to reference missing data
Variables come up blank
Messages dont send
Think of it like trying to read a letter that was never delivered. The mailbox (flow) exists, but theres nothing inside.
The Right Approach
Option 1: Use the same trigger type
Flows triggered the same way (same exact trigger or webhook with identical payload) can reference each others data properly.
Option 2: Restructure your logic
Sometimes its better to keep flows separate based on their trigger sources rather than connecting them.
Bottom Line
Flow navigation works fine between compatible trigger types
Webhook data only exists when the webhook fires
Bypassing a webhook trigger means bypassing the data it provides
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 dont align.