Webhook events
The fourteen events a webhook can receive, the fields each payload carries, and how to subscribe to some but not all.
Fourteen events are emitted. The seven below cover calls, leads and the
workspace; the seven campaign webhook events
cover outbound campaigns. Each arrives in the standard
webhook envelope, with these fields under data.
| Event | When | Payload fields |
|---|---|---|
conversation.started | As a call begins, when its session record is created | sessionId, agentId, channel, source, callStartedAt, isTest, and campaign on a campaign call |
conversation.ended | At call teardown | sessionId, agentId, channel, callEndedAt, duration_seconds, isTest, leadRequestId on a lead callback's call, and campaign on a campaign call |
call_log.completed | After post-call analysis, on the first analysis of a call only | sessionId, agentId, agent_name, channel, outcome, sentiment, summary, duration_seconds, message_count, caller_number, caller_name, end_reason, occurred_at, ended_at, simulated, request_context, booking ({ uid, start } or null), linked_references, leadRequestId on a lead callback's call, and campaign on a campaign call |
alert.fired | When an alert rule fires | alertId, alertName, metricKey, alertType, fireId, value, baseline, metricLabel, valueLabel, baselineLabel, reason, firedAt, sessionId |
metric.optimised | When a scheduled metric optimiser run completes | metricId, metricName, sessionId, outcome, agreementBefore, agreementAfter |
lead.received | Once for every lead the lead callback URL records, whatever happens to it | leadRequestId, agentId, agent, status, reason, submittedAt, dialAt, sessionId, timezone, name, phone, fields |
lead.updated | When a recorded lead reaches its final status: called, failed or turned away | The same fields as lead.received |
Notes
call_log.completed fires on the first analysis only: re-running analysis does
not re-send it.
The two conversation events carry an isTest flag so you can separate test
traffic from real callers.
channel is telephony for a phone call, webrtc for a browser call, teams
for a Teams call and chat for a chat.
leadRequestId is the id the lead callback webhook answered when it accepted
the lead, so a lead you posted can be matched to its call. A lead accepted
outside the calling window is answered scheduled with no session yet; its
call's events carry the same leadRequestId when the agent rings it. The field
is absent on every other call.
end_reason says how the call ended: caller_hangup, agent_end_call,
transfer_to_human, idle_timeout, no_input_hangup, max_duration,
connection_lost (a browser call whose connection dropped before either side
hung up), or one of the guardrail and dialling reasons. It is null when the
session recorded none.
Payloads are metadata: identifiers, timestamps, durations, and the analysis
verdict. call_log.completed also carries the summary, the caller's number
and the name the caller gave, and the lead events carry what the lead was
posted with. The transcript is never sent.
Every event's body, with each field's type, is in the webhooks section of the
OpenAPI specification, so
a client generator can build types for your receiver.
Campaign calls
When an outbound campaign placed the call, the three
conversation events carry a campaign object, so you can match the call to
the list you imported without a second lookup.
{
"event": "call_log.completed",
"data": {
"sessionId": "3f2a9c1e-…",
"agentId": "0c9e1d2f-…",
"outcome": "completed",
"campaign": {
"id": "9d4b2e70-…",
"name": "November outreach",
"recipientId": "41c7a8e3-…",
"stepId": "call-2",
"attempt": 2,
"redial": false,
"callback": false,
"callbackAt": "2026-11-10T04:00:00.000Z",
"texts": [
{
"stepId": "sms-1",
"sentAt": "2026-11-06T02:14:09.000Z",
"status": "delivered",
"reply": null,
"repliedAt": null
}
]
}
}
}| Field | Meaning |
|---|---|
id | The campaign's id |
name | The campaign's name when the event was sent |
recipientId | The recipient's id, the Recipient ID column of the campaign export and the id get_campaign_recipient takes |
attempt | Which attempt at this recipient it was, counting from 1. A double dial redial carries the number of the attempt it belongs to, so it never counts as another attempt |
redial | true on the double dial's second call, the one rung straight after an unanswered first ring; false otherwise |
callback | true when this call is a callback the person asked for, which uses no attempt; false otherwise |
callbackAt | When the recipient's next callback is booked for, as an ISO 8601 time, for example the one the person booked on this call; null when none is booked |
stepId | The step of the sequence this call belongs to; null on a call placed before steps were recorded |
texts | Every SMS the sequence has sent this recipient so far, oldest first: its stepId, sentAt, status (sending, accepted, delivered or failed), and the person's reply with repliedAt, or null. Empty when none was sent. See SMS steps |
The field is absent on every other call, and on a campaign call placed before attempts were linked to their calls in November 2026.
The campaign's own launch, pauses and completion, and each recipient's final result, are separate events: see Campaign webhook events.
Lead events
The two lead events report every lead posted to an agent's lead callback URL, including the ones the agent does not ring. A lead the URL refuses before it is recorded (an invalid phone number, an unreadable body, a rate limit) gets an error answer and no event.
{
"id": "5b0c3c58-3f0e-5a41-9d6e-0b8f6f1d2a7c",
"event": "lead.received",
"data": {
"leadRequestId": "8f14e45f-ceea-4e7a-9a3b-2c1d5e6f7a8b",
"agentId": "0c9e1d2f-…",
"agent": "acme/reception",
"status": "scheduled",
"reason": null,
"submittedAt": "2026-11-04T13:05:12.481Z",
"dialAt": "2026-11-05T01:00:00.000Z",
"sessionId": null,
"timezone": "Australia/Perth",
"name": "Sam Lee",
"phone": "+61412345678",
"fields": { "message": "Quote for a deck", "source": "web form" }
}
}| Field | Meaning |
|---|---|
leadRequestId | The id the lead callback URL answered with. The same id is on the call's conversation.ended and call_log.completed |
agent | The agent's handle, workspace-slug/agent-slug |
status | calling, scheduled, duplicate, rejected or failed on lead.received; dialled, failed or rejected on lead.updated |
reason | Why a lead was rejected or failed, for example do_not_call, queue_full, trigger_daily_cap, expired or the dial's error code. unconfirmed on a dialled lead means the call may have gone out but the platform could not confirm it |
submittedAt | When the lead was recorded, UTC |
dialAt | When the agent rings, or rang, the lead, UTC. null for a lead it never rings |
sessionId | The call's session, once the agent has rung the lead |
timezone | The time zone the calling hours were read in: the timezone the lead was posted with when it is a valid IANA name, otherwise the agent's |
name, phone, fields | What the lead was posted with: the name, the number in international format, and the other form fields |
lead.received tells you what the platform did with the lead the moment it
arrived. A lead it rings at once arrives as calling, then lead.updated
says dialled with the sessionId, or failed. A lead outside calling hours
arrives as scheduled with its dialAt, then lead.updated says dialled,
failed, or rejected with reason expired if it could not be rung within
a day. A lead that is a duplicate, rejected or failed on arrival gets no
lead.updated.
Each event has its own id for one lead and status, and every retry of it
carries the same id. Events can arrive out of order, so store each lead by
leadRequestId and never let calling or scheduled replace a final status.
Choose which events an endpoint receives
Expand a webhook row to reach the per-event toggles, grouped as Conversations (started, ended, analysis complete), Leads (received, status changed), Campaigns (launched, scheduled, paused, resumed, completed, cancelled, recipient finished) and Workspace (alert triggered, scoring improvement ready). A new webhook is subscribed to all fourteen. A webhook created before the lead or campaign events existed has them switched off until you turn them on. Switching one event off leaves the others delivering.