Skip to main content
Go to Flow transfers the contact into another published Flow and continues there. Use it to keep each Flow focused and under size limits.

​
Why modular Flows win

  • Stay under the 250 blocks per Flow cap
  • Reuse shared routines (FAQ, payment, handoff)
  • Let different teammates own different Flows
  • Ship safer changes by updating one child Flow at a time

​
Set up a handoff

1

Publish the destination Flow

The child Flow must be published before the parent can send contacts into it.
2

Add Go to Flow

In the parent Flow, add Go to Flow and select the destination.
3

Pass context via the contact

Contact fields and tags persist. Set any fields the child needs before the handoff.
4

Test the full path

Run Test Flow from the parent and confirm the child path executes.

​
Patterns

Go to Flow keeps contact context. It does not create a separate anonymous session. Design fields as your contract between parent and child.

​
Avoid loops

Do not create A → B → A cycles without an exit Condition. Loops burn trust and can look like spam.

​
Next

Conditions

Decide which child Flow to open.

Best practices

Naming and modularity guidelines.