Skip to main content
A post-call webhook is a server notification associated with a completed or failed call. It can support downstream review or business processing once its event and delivery contract is released.
Workspace notification preferences persist, but the current webhook-resource CRUD is placeholder behavior. Creating a resource returns an identifier without verified persistence. There is no verified delivery, signature, retry, or callback-log implementation. Do not use the current create response as evidence of a working receiver.

​
Configuration shape

Workspace settings expose webhooks.post_call_webhook_id, webhooks.events, and webhooks.transcript_format. Agent-specific intent belongs under platform_settings.workspace_overrides.webhooks. Transcript format accepts json or opentelemetry. Use Get Agents Platform settings and Update Agents Platform settings to inspect the committed contract. The dashboard currently reads the selected post-call default; it is not a verified end-to-end setup wizard.

​
Prepare a receiver

No signature-header name, payload envelope, or retry schedule is promised here. Add executable receiver examples when those contracts are released and verified.

​
Frequently asked questions

No. Preference storage and webhook resource persistence are separate. Current resource CRUD does not establish a working registration.
No verified collector delivery is established. Review OpenTelemetry for the supported stored-data distinction.