End Flow
Stop the current flow and return control to the caller – the flow that used Go to Flow to enter this one.
The End Flow node terminates the current flow and returns control to wherever this flow was called from. If the flow was entered via a Go to Flow node, execution resumes in the calling flow immediately after that node.
Available in: Conversational Flows and Handlers
End Flow vs End Conversation
| End Flow | End Conversation | |
|---|---|---|
| What stops | The current flow | The entire conversation session |
| Execution continues | ✅ Returns to the caller flow | ❌ Session is terminated |
| Use when | A sub-flow has finished its job | The conversation is over |
Use End Flow for modular flow design – it lets you break logic into reusable sub-flows that return cleanly when done. Use End Conversation to terminate the user's session entirely.
Usage
End Flow is typically placed at the natural conclusion of a sub-flow, after the final response has been sent:
[Product lookup sub-flow]
→ [Find Records: match product by name]
→ [Cards from Table: show results]
→ [End Flow] ← returns to the Core flow that called thisEnding a flow resets checkpoints
Ending a flow also resets its currently active Checkpoints. If the flow was paused at a Checkpoint earlier in the conversation, that resumption point is discarded the moment the flow ends – the next user turn goes through the normal Handler and Flow routing from the beginning, instead of resuming mid-flow.
Flows without End Flow
If a flow reaches its last node and there is no End Flow, execution still stops at the flow boundary – the pipeline does not error. End Flow is explicit and makes the intent clear, but is not strictly required at the end of a linear flow.
In branching flows, End Flow on each branch ensures every path has a clean exit, preventing accidental fall-throughs.