Storing values for later steps
The Set node (action_set) writes key → value pairs into scenario state (constants or process variables, depending on the template). It does not send a chat message: it is an internal step for the logic you build on the canvas.
Typical tasks
- Set a flag (e.g. registration completed).
- Store a selected or computed value for the Router or later nodes.
- Prepare context before operator connect or another action.
In the editor
- Add Set (
action_set) from Data / templates. - In Node Inspector, set keys and values (often with
{{...}}placeholders). - Connect the output to the next node.
Full fields: Set parameters.
⚠️ Ordering relative to operator connect (Fast Line)
If a Set (or Clear constant) node sits before the connect-to-operator node — especially in Fast Line scenarios — its changes may not reach the nodes that run after the operator step (for example, an action-jail that reads that constant). The operator-connect step saves dialog state in a separate cycle that can overwrite values set immediately before it.
Rule: constants that later steps depend on after the operator (counters, iterators, flags) should be set/reset with the Set node after the connect-to-operator node, not before it.
| Set / Clear constant position | Result |
|---|---|
| Before connect-to-operator | The change may be lost — later steps see the old value |
| After connect-to-operator | Works reliably — later steps see the new value |