Variables and Context

Nodes read and write values as a conversation runs: what the customer said, the matched intent, a service's answer, a value you calculated. These values are the conversation's context, and each one is held in a variable. Part of Flows.

Inserting a variable

In any node input that accepts variables, type % to open the picker, then choose a variable. When the input is used, the variable is replaced with its current value. A name you type after % can be up to 36 characters long and use letters, digits, ., [ and ].

The picker groups variables by kind, and which groups you see depends on the flow type:

Static variables

The platform fills these in. The most useful ones:

You can assign a static variable yourself, but the platform overwrites it the next time it sets that value.

Dynamic variables

A dynamic variable has a Key (its name) and a Value. The Value is a JavaScript expression, worked out each time a node uses the variable. Dynamic variables belong to the project version, so every flow in it sees the same list, including intent action flows and AI Agent tool flows.

To create one, type % in a node input and select + (Add Dynamic Context) in the list. In the Create dynamic context window, fill in:

• Key: no spaces.
• Value: required. It cannot contain a double quote, a backtick or a semicolon.

⚠️ Warning: The Value is worked out again every time the variable is used. If a Code or Variable node assigns a dynamic variable whose Value returns something, the next use replaces the assigned value with the Value's result. To carry a result from a Code node, set the Value to null.

For example, to keep a customer tier that a Code node works out:

1. Create a dynamic variable with Key CustomerTier and Value null.

2. In a Code node, assign it:

   javascript context.dynamic.CustomerTier = "Gold";

3. Later nodes, in this flow or any other flow, can use %CustomerTier and get Gold.

Custom variables

Any JavaScript global in the conversation is a custom variable. Examples are the output name you give an HTTP node, a name assigned in a Variable node, and a name a Code node assigns without declaring it. To use one, type % and then its name. The picker offers whatever you type as a Custom mention.

A custom variable lasts for the whole conversation and is visible to every flow the conversation enters. It is not kept after the conversation ends.

Setting values in a flow

Variable node

The Variable node has one required input, Operation, which holds a single JavaScript statement, for example:

paymentAttempts = 0

The statement runs in the conversation's global scope, so paymentAttempts becomes a custom variable. The node has one output.

Code node

The Code node runs JavaScript. Your code runs inside a function:

• Names declared with var, let or const exist only inside that Code node.
• Names you assign without declaring them become custom variables, which later nodes can use.
• Dynamic variables are available as context.dynamic.<Key>.
• No helper libraries are loaded.

For example, to check that a customer number collected into the CustomerNumber dynamic variable has eight digits:

var raw = "" + context.dynamic.CustomerNumber; customerNumberIsValid = /^[0-9]{8}$/.test(raw);

raw stays inside the node, and later nodes can branch on %customerNumberIsValid.

Reading values from the incoming message

In the Create dynamic context window, Select element from activity lets you pick a value from the message the channel sends, and use it as the variable's Value.

SIP headers

On a voice channel, the SIP headers of the call are under SipInfo > Headers. In the tree you can select only the Headers object as a whole. To read one header, type the Value yourself:

Give the dynamic variable a key such as SipCustomerId, then use %SipCustomerId in any node. You can also read the same path in a Code node.

Location

When the customer shares a location, for example on WhatsApp, read it from the static variables LocationLatitude and LocationLongitude.

How long values last

Each time the conversation returns to the start of the Main flow, these values are cleared:

• LastUserInput, LastInputType, LastIntent, LastIntentConfidence and CurrentVirtualAgent
• the LastAiAgent values
• intent entities

Everything else lasts for the whole conversation: dynamic, custom and project entity variables, and the other static variables.