Webhook meaning: how call data reaches your CRM
Jaseem Abbas
- Published
How does a webhook work?
A webhook works in reverse of an ordinary API call: instead of your system asking for data, the other service sends it to you the moment an event happens. The Standard Webhooks specification (read 15 November 2026) puts it this way: webhooks are a common name for HTTP callbacks and a way for services to notify each other of events, "a sort of a reverse API".
You set it up once: you give the sender a web address, called the endpoint, that your system listens on. When the event happens, the sender posts a message to that address, and your system answers to say it arrived. The specification treats any 2xx status code, 200 to 299, as a success and every other outcome, a 404, a 500 or a timeout, as a failure.
Picture Rohit, who runs sales operations at a Bengaluru solar installer. His team's AI voice agent calls new enquiries. When a call ends, the agent's system posts a message to his CRM's address: the lead's phone number, the outcome "site visit booked" and the date the lead chose. The CRM moves the lead to the right stage before the next one rings. Rohit, the installer and the fields are made up for this example.
What does a webhook send?
A webhook sends a payload: a small message, nearly always in JSON, that says what happened and gives the details your system needs. RFC 8259 defines JSON as a lightweight, text-based, language-independent data interchange format, so almost any CRM or automation tool can read it.
For a call, a payload can hold things like the following.
Field: Call ID
- What it tells your system
- Which call this is
- Example
- call-48213
Field: Outcome code
- What it tells your system
- How the call ended
- Example
- site_visit_booked
Field: Extracted values
- What it tells your system
- What the agent learned from the caller
- Example
- preferred date: 21 November
Field: Duration
- What it tells your system
- How long the call ran
- Example
- 3 minutes 40 seconds
The Standard Webhooks specification adds two rules for the receiver. Verify that a message really came from the sender, using a signature made with a secret key both sides share. And answer before the sender gives up, because a timeout counts as a failure.
How does AI change webhooks?
It changes what is inside them: instead of a bare "call completed" signal, the webhook can carry what the agent understood on the call. A call from an AI voice agent produces a transcript, an outcome code and answers to the questions it asked, and a webhook can pass those on as fields your CRM can use.
The webhook is also the return path for function calling. An agent that uses function calling reaches into your system during the call, to look something up or book a slot. A webhook is the other direction: after the call, your system hears what happened, without anyone asking.
On Bananaflow, a Webhook node posts any JSON you design when a call finishes. Each call also records an outcome code from the agent's own list, values the agent extracted, a QA score, tags, sentiment and a summary, and call events can be exported to BigQuery. You can start calls from your own system through the API, n8n or Zapier, and get the results back by webhook. To see what is recorded, read how Bananaflow records each call's outcome, summary and extracted fields; for the outcome codes, see call disposition codes.
What is the difference between a webhook and an API?
An API is a request you make; a webhook is a message you receive. With an API, your system calls the service whenever it wants data, which means asking again and again to find out whether anything changed. With a webhook, the service calls you once, when there is something to tell.
Most systems use both. A voice agent calls your order API during the call, and your CRM receives a webhook after it.
FAQ
Frequently asked questions
What is the meaning of webhook?
A webhook is an HTTP callback. When an event happens, such as a call ending, one service sends a message to a web address you gave it, so your system learns about the event without having to ask.
What is the difference between a webhook and an API?
With an API, you ask a service for data when you want it. With a webhook, the service tells you when something happens. The Standard Webhooks specification calls webhooks a sort of reverse API.
What is in a webhook payload?
A payload is the message the webhook carries, usually JSON. For a call it might hold the call ID, the outcome code, values the agent collected and the duration. On Bananaflow, you design the JSON a call webhook posts.
How does the sender know a webhook arrived?
By the response. The Standard Webhooks specification treats a reply with a 2xx status code, 200 to 299, as success and anything else, including a timeout, as a failure.
What happens if my server is down when a webhook is sent?
The specification recommends that the sender retry the delivery on a schedule, with growing delays, over several days. Your receiving server should answer with a 2xx status before the sender's timeout, since a timeout counts as a failure.
How do I know a webhook is really from the sender?
Check its signature. The Standard Webhooks specification says webhooks are just HTTP requests from an unknown source, and recommends a signature made with a secret key shared by both sides, plus a timestamp, so the receiver can verify it.
How does call data reach a CRM through a webhook?
The webhook posts the call's result to an address on your side, such as an endpoint of your CRM or an automation tool. Your system reads the JSON and updates the lead, so no one copies results by hand.
Can a webhook start a call?
A webhook carries results out. To start calls from your own system, Bananaflow takes calls started through its API, n8n or Zapier, and a campaign can call a list from a CSV. Results then come back to you by webhook.
