Webhooks
Webhooks send call results to your systems — a CRM, a helpdesk, your own reports — without you asking for them. This page shows what arrives and how to read it.- Where to set one up — on the agent, in the Webhooks section of its settings: see Webhooks. A webhook belongs to one agent; for several agents, add the endpoint to each.
- How delivery works — signing, retries, duplicates and order: see Webhooks in the Web API.
Two events
call_ended— right after the call finishes: the outcome, the transcript, the variables. It comes early, so post-call analysis is not there yet, and the recording is usually still being processed.call_analyzed— once post-call analysis and the recording are ready. It carries the complete call as well, so if you only need the final picture, subscribe to this one event alone.
Example: call ended
Here is a samplecall_ended webhook payload that HubTalk AI v4 may send to your endpoint:
Example: analytics ready
The same call block as incall_ended, plus the analysis results:
Event fields
Times everywhere are Unix epoch seconds (fractional). An empty string is"", a missing number is null.
Common fields
The call block — in both events
The recording — recording
In call_ended the block sits inside call, in call_analyzed it is at the top level. The field is absent if the call was not recorded.
Only in call_analyzed
Both events carry an
error_code field — the numeric failure code assigned by the telecom operator (for example 486 with status_reason = busy). It is null when the operator reported no code. Operators interpret these codes differently — do not build strict logic on them without checking with your own operator. Note as well that busy and user_declined are distinct reasons: a busy line and a subscriber hanging up are told apart.
If analysis was skipped or failed, call_analysis is empty and a reason field explains why, for example voicemail or no_speech. When the call has a recording, call_analyzed also includes a top-level recording_url and a recording object once the recording is ready — call_ended carries the same recording block, but it is often still processing at that point.
Unanswered calls carry variables too
A call that never connected — no answer, busy, a failure, an answering machine — still produces a webhook, and that webhook carriesdynamic_variables: the values you supplied for the contact when the call was queued. Nothing was collected during the conversation, because there was no conversation, but the input of the call is there.
Three surfaces show the same thing: the call variable inside post-call functions, the dictionary in the call-ended webhook, and GET /v1/calls/{call_id} in the Web API — for one call the data agrees.