Webhook actions

The webhook can respond with zero, one or more of those actions:

• Set one or more session variables. The updated values are attached to the current call session and returned in the following executions of the webhook. If the variable already exists, the existing value is updated. Otherwise, a new variable is created with the given value.
• Change the current event filters. Normally, the webhook is called for every event or session variable change, but you can reduce the executions to a filtered list of events.
• A list of flow nodes to disable for the remainder of the call session. See Node overrides for more information.
• Start an operation asynchronously, using the given parameters.

Many operations require valid parameters: If they are invalid or missing, the flow sends OPERATION_ERROR event to the webhook with some attached information about the error (in the form of session variables).

Node overrides

Internally, the sequence of activities and call events are implemented with nodes that divide the overall sequence into smaller blocks, each responsible for a small fraction of the overall logic. The webhook prevents some of those nodes from executing their logic by listing them by name in the session’s node overrides.