Skip to main content

End Node

The End Node marks the natural end of a flow.

What it serves​

When the flow reaches an End Node, it terminates cleanly. Any returns, final outputs, or session updates that need to happen should be done in the nodes leading up to it.

When to use it​

  • At the end of any branch where a flow should finish normally.
  • Use one End Node per terminating branch — multiple End Nodes in a flow are fine.

Connections​

  • Inputs only.
  • No settings beyond rotation.

The single terminator​

The End Node is the only terminator. (Earlier builds documented separate Stop and Exit nodes — those have been removed.) For an early exit on a guard, route a Condition Node into an End Node; to hand control to another flow, use Jump Flow.

When the root flow reaches its End Node it emits a { final: true } terminator — the signal the client watches for to stop the run and trigger end-of-flow cleanup. A child flow's End Node ends that child without tearing down its parent. You don't strictly need an End Node (a dangling output dot also ends a branch), but it makes the intent explicit and is what cleanly closes a Parallel Context clone so its result merges back.