Post-Call Webhook
Post-Call Webhook
Post-Call Webhook
Add a webhook URL to the request in order to receive information after the call.
external_webhook_url key with the URL of your webhook receiver.Include the following key-value pair in your API request body:
Upon completion of the call, the webhook URL will receive a response like the following. In this case, the agent has three information extractor actions to get information after the call is completed.
The call object in the webhook response contains a status field which can have various values, each indicating a different state of the phone call. Below is a table explaining these statuses:
This end_call_reason parameter provides insight into the reason why a call ended:
When a call ends due to a custom end-call reason, the response also includes a custom_end_call_reason field with the specific condition that triggered the termination (e.g., "Customer is being abusive").
The analysis object contains automated quality assessments generated after every call. Each field evaluates a specific aspect of the conversation and returns one of the following values:
true — the criterion was metfalse — the criterion was not metpartial — the criterion was partially met (only for fields that support it)not_applicable or null — the criterion does not apply to this callEvery field also has a corresponding _feedback field (e.g. persona_feedback) that provides a short explanation when the result is not true. Feedback is empty when the criterion is fully met or not applicable.
The collected_variables field contains the collected variables (slots) from your conversation flow. This allows you to access user-provided information programmatically.
The object contains the variable names as keys, with each variable having:
Example:
Only variables with collected: true are included in the response. System variables and variables with collected: false are filtered out.
Synthflow does not enforce a fixed maximum payload size for post-call webhooks. In most payload size incidents, the receiving endpoint rejects the request because of its own request body limit.
Yes. Your receiving system can return HTTP 413 Payload Too Large when the webhook body exceeds its configured limit. This is common when calls are long, transcripts are large, or many actions are included in one payload.
Start by checking your endpoint logs for HTTP 413 responses. Then increase the accepted request body size in your webhook receiver and any proxy in front of it, such as Cloudflare, API Gateway, Nginx, or your app server. If needed, reduce payload size by disabling transcript storage downstream or trimming what you persist.