Nodes

Jump to

Redirect the Flow to another node.

The Jump to node (jump) moves execution to another node within the same Flow. It is used to avoid visual repetition of connections on the canvas.

Fields

Destination node: ID of the node to jump to.

Rules

The destination must exist in the Flow.
The destination cannot be the jump node itself.
Compatible types are: conversation, message, branch, trigger_subflow, custom_action, during_call_sms, transfer, booking, end, placeholder.

Beware of cycles

Jumps that form cycles are allowed. Validation only flags them when no path inside the cycle can end the call — make sure there is a way out (a branch with a path to end).

Split path

Create branches with deterministic or LLM prompt conditions.

Trigger subflow

Trigger another reusable Flow during the call.