Backdrop Webhook Event Types
The two events Backdrop sends, call.summary.created and call.no_show.created, when each one is sent, and every field they carry.
Backdrop sends two events. Every event has the same shape: its type, the
timestamp it was sent at, and the call in data.
| Event | When it's sent | Use it to |
|---|---|---|
call.summary.created | A call's summary is ready | Log the call and its summary in your CRM |
call.no_show.created | The buyer didn't show up | Flag the meeting and get it rescheduled |
call.summary.created
Sent once a call ends and Backdrop has written its summary, usually a minute or two after the call. This is the event most teams use to log calls in their CRM.
{
"type": "call.summary.created",
"timestamp": "2026-11-11T18:01:05.000Z",
"data": {
"id": "0b6f8a52-6f0f-4c59-9b55-2a4d1f3c7e10",
"title": "Acme discovery",
"startedAt": "2026-11-11T17:30:00.000Z",
"endedAt": "2026-11-11T18:00:20.000Z",
"durationSeconds": 1820,
"userInfo": { "id": "user_2abc", "email": "dana@seller.com", "name": "Dana Rep" },
"account": { "name": "Acme", "domain": "acme.com" },
"attendees": [
{ "name": "Dana Rep", "email": "dana@seller.com", "team": "selling" },
{ "name": "Sam Buyer", "email": "sam@acme.com", "team": "buying" }
],
"summary": "Acme wants a 30-seat pilot in Q1. Sam owns the budget and needs a security review first."
}
}call.no_show.created
Sent when the buyer was expected on a call and nobody from their side took part. It comes in two cases:
- The rep recorded, but no buyer joined. You get
call.summary.createdfor the call too. - Nobody spoke at all. Backdrop doesn't keep a silent call, so this is the only event you get. Its title and company come from the calendar meeting.
It carries the same call fields as call.summary.created, without summary.
{
"type": "call.no_show.created",
"timestamp": "2026-11-11T17:41:00.000Z",
"data": {
"id": "0b6f8a52-6f0f-4c59-9b55-2a4d1f3c7e10",
"title": "Acme discovery",
"startedAt": "2026-11-11T17:30:00.000Z",
"endedAt": "2026-11-11T17:40:00.000Z",
"durationSeconds": 600,
"userInfo": { "id": "user_2abc", "email": "dana@seller.com", "name": "Dana Rep" },
"account": { "name": "Acme", "domain": "acme.com" },
"attendees": [
{ "name": "Dana Rep", "email": "dana@seller.com", "team": "selling" },
{ "name": "Sam Buyer", "email": "sam@acme.com", "team": "buying" }
]
}
}The call's fields
| Field | What it is |
|---|---|
id | The call's ID in Backdrop. Both events for the same call have the same id. |
title | The call's title |
startedAt, endedAt | When the call started and ended, in UTC |
durationSeconds | How long the call lasted, in seconds |
userInfo | The rep who recorded the call: id, email and name |
account | The company the call was with: name and domain |
attendees | Everyone on the meeting: name, email, and team, which is buying, selling or unknown |
summary | The post-call summary. call.summary.created only. |
To find the call's records in your CRM, match on account.domain and the
attendees' emails rather than names. They're the same in Backdrop and in your
CRM.
New fields may be added to events over time. Existing fields aren't renamed or removed.
Overview
Backdrop webhooks send every call's summary, company and attendees to Zapier, Clay, a HubSpot workflow or your own endpoint the moment the call ends. Enterprise workspaces only.
Zapier
Catch each Backdrop call in a Zap with Webhooks by Zapier, then log it on the right company and contacts in HubSpot, Salesforce or any CRM Zapier connects to.