Webhook Configuration
To enable conversation ended webhooks:- Use the Enable Conversation Ended Webhook API endpoint
- Provide your webhook URL where notifications will be sent
- Optionally configure post-call variables on your assistant to extract structured data from conversations
Request Format
The webhook is sent as a POST request to your configured URL with the following JSON payload:Payload Structure
Numeric identifier of the conversation (the same id shown in the dashboard conversation URL). Use
conversation_id (UUID) when calling the API.Variables that were passed to the assistant at the start of the conversation (e.g., from pre-chat form fields or automation flows)
Media files (images, videos, documents) shared during the conversation. Each entry includes a direct URL you can pass to external services (for example, image or video analysis). This is an empty array when no media was shared — media is typically present on WhatsApp conversations.
When it fires
A conversation is considered ended when the customer has sent nothing for the assistant’s inactivity timeout (30 minutes by default; change it in the assistant’s conversation settings). The post-conversation variables are extracted first, then the webhook is sent. If the assistant allows re-triggering, a later message reopens the conversation and a new webhook is sent when it ends again.Delivery and retries
The webhook is aPOST with a JSON body. Reply with any 2xx status within 10 seconds; the response body is ignored.
Temporary failures are retried with a growing delay: up to 5 attempts in total, 30 seconds, 60 seconds, 2 minutes and 5 minutes apart, so the last attempt is made about 8.5 minutes after the first. Retried: any 5xx, 408, 429, connection failures and timeouts. Any other 4xx is treated as a problem with the endpoint and is not retried.
The conversation page in your dashboard shows the status and body of the latest attempt, and lets you Re-send webhook at any time. To send several again, use Resend Webhooks in the conversations list (it evaluates them again first, up to 500 at a time) or the Resend conversation webhooks endpoint (stored data, up to 500 per request). Because of retries and manual resends the same conversation can arrive more than once: de-duplicate on conversation_id.
Important Notes
- The
conversation_idandassistant_idare UUIDs, not integer IDs assistant_id,assistant_name, andtypelet a single webhook URL serve several assistants — route on them instead of configuring a separate endpoint per assistant- The
senderfield is only populated for WhatsApp conversations — it will benullfor web widget conversations - The
customer_phoneis only available for WhatsApp conversations - The
customer_namecomes from pre-chat form data or conversation context - Timestamps use the user’s configured timezone (ISO 8601 format)
- The
extracted_variablesare populated from your assistant’s post-call schema evaluation. Tags with multiple values, objects, lists, and JSON arrive as arrays or objects, not strings - The
input_variablescontain data from pre-chat forms (web widget) or automation flows - The
attachmentsarray lists media (images, videos, documents) shared during the conversation, each with a downloadableurl— useful for forwarding to external analysis tools. It is an empty array when no media was shared (most common on web widget conversations)

