Operational Parameters

Values a contact centre maintains outside its contact flows, so routing and messaging behaviour can change without editing a flow. Each parameter has a unique name, a type, a value, and a status that controls whether contact flows resolve it.

📄️List operational parameters

List every operational parameter defined for the contact centre, with its type, current value, and status.

📄️Create operational parameter

Create an operational parameter. The name must be unique within the contact centre and may contain letters, numbers, hyphens, underscores, and plus signs. The value must match the chosen type; a TABLE parameter supplies a table schema of up to 20 columns instead of a single value.

📄️Create operational parameter with custom value

Create an operational parameter. The name must be unique within the contact centre and may contain letters, numbers, hyphens, underscores, and plus signs. The value must match the chosen type; a TABLE parameter supplies a table schema of up to 20 columns instead of a single value.

📄️Get operational parameter

Retrieve a single operational parameter by name.

📄️Update operational parameter

Update the name, description, type, value, or status of an operational parameter. Omitted fields are left unchanged.

📄️Update operational parameter with custom value

Update the name, description, type, value, or status of an operational parameter. Omitted fields are left unchanged.

📄️Delete operational parameter

Delete an operational parameter. Contact flows that reference the name no longer resolve a value.

🗃Table Rows

2 items

🗃Custom Types

5 items