State variables

State variables hold data your agent captures or updates during a call — as opposed to variables, which are set before the call starts.

​

Declare a state variable

A state variable is a key and a defaultValue — the value it holds until the agent updates it during the call.

​

Capture state in Pathways

In a Pathways agent, conversation nodes can declare state captures — data the agent should extract from the caller at that step, with a description to guide it. Transitions can also declare state updates, setting a state variable’s value as the agent moves to the next node.

​

Update state outside Pathways

On a Single Prompt agent, the agent updates state using the updateCallState tool. It can only set keys you’ve declared as allowed for the agent — this keeps the agent from writing arbitrary state during the call.

​

Reference state later

Reference a state variable’s current value in your prompt with {{state.variableKey}}. State variables also feed into other parts of the platform:

• Call outcome classification can take final state into account.
• Post-call webhooks can include state values in their payload, and use them as trigger conditions.

​

Next step

Tool calls to let your agent take actions during the call.