A global node can be reached from every other node without drawing an edge to it. Use global nodes for things a caller can bring up at any moment: "can I talk to a person", "what are your opening hours", "stop calling me", or an emergency.
Make a node global#
- Select the node and open Node settings.
- Turn on Global node ("Jump here from any node when the condition is met.").
- Write the condition, for example "The user asks to speak to a human".
- Optional: add Go back when conditions and a Cool down (user turns).
On the canvas, a global node has a dashed border and a Global badge.
Fields#
global_node_setting on any node:
| Field | Type | Description |
|---|---|---|
condition |
string | When to jump here. Judged by the LLM like a prompt transition |
go_back_conditions |
array of {id, transition_condition} |
When to return to the node the caller came from |
cool_down |
integer, 0 to 100 | After leaving, this node cannot trigger again for this many caller turns |
{
"id": "node_hours",
"type": "conversation",
"name": "Opening hours",
"instruction": { "type": "prompt", "text": "Tell the caller our opening hours: 8am to 6pm weekdays, 9am to 1pm Saturday." },
"edges": [],
"global_node_setting": {
"condition": "The caller asks when we are open",
"go_back_conditions": [
{ "id": "go_back_1", "transition_condition": { "type": "prompt", "prompt": "The caller's question about hours is answered" } }
],
"cool_down": 3
}
}How global nodes trigger#
Global conditions are offered to the LLM together with the current node's prompt transitions, as transition_to_<node_id> functions. They are checked from every node, except:
- the global node itself (while you are in it), and
- global nodes still in their cool-down.
Because they share the prompt step, equation transitions and always edges of the current node win over global nodes.
Going back#
When the flow enters a global node from another node, the engine remembers where it came from. Go back when conditions describe when to return there:
- Prompt go-back conditions (the dashboard's form) are offered to the LLM as a transition back to the origin node.
- Equation go-back conditions (API) are checked first, without an LLM call.
- Both (
equation_prompt) go-back conditions are offered only when their equations hold.
If a global node has no go-back conditions, it behaves like any other node: it follows its own edges, or stays.
Returning records the transition type global_go_back, or interrupt_go_back when the caller interrupted the global node's speech. Entering a global node records global.
Cool-down#
cool_down counts caller turns after the flow leaves the global node. Until that many turns have passed, the node is not offered again. Unset or 0 means no cool-down. Use it for nodes that the LLM might re-trigger straight after answering, such as an FAQ node.
Global nodes in components#
Global settings inside a component are dropped when the component runs: those nodes are not global in the parent flow.
Gotchas#
- Write global conditions narrowly. A broad condition ("The caller has a question") fires constantly and pulls the call out of the main path.
- The more global nodes a flow has, the more transition functions the LLM sees on every turn.
- A global node with Prompt instruction and no edges or go-back conditions keeps the call there. Add a go-back condition or edges onwards.