Skip to main content
A state update would change values used during a conversation, such as a selected product or a completed verification step. Define who owns each value and which action is allowed to change it before designing that behavior.
update_state is not an accepted built-in tool type in the current API. Do not add that type to an agent or assume a state-update callback exists. This page covers preparation and adjacent authoring features.

​
Separate the kinds of state

Changing a placeholder edits example configuration. It is not a live customer-data update. Changing an agent draft is also separate from changing values inside an active conversation.

​
Prepare a tool-result assignment

The current assignment contract includes: These fields describe assignment intent. They do not establish that live assignment or sanitization is implemented. Do not treat sanitize: true as verified protection for a sensitive value.
1

Define the value and source

Choose a non-secret variable name and an actual response field from a reviewed tool contract. Record the expected type and what should happen when the field is missing.
2

Review the definition

Use the supported tool configuration workflow to inspect or author assignments. Keep reserved platform names and credentials out of general-purpose variable slots.
3

Inspect stored configuration

Reopen the tool and check the assignment path and destination name. Keep live assignment testing pending until the relevant execution path is available.

​
Frequently asked questions

A placeholder cannot perform identity verification or grant access. The service responsible for that decision must establish and enforce it.
No database write is established by this configuration. Durable business changes belong to a separately authorized service action.