Skip to main content
Brilo can tell another system what happened the moment a call ends, sending the summary, the written record, and the details your agent collected. This is called a webhook. It needs someone technical to set up, usually about an hour, and it works on every plan including Free.

​
What it is

A webhook is a message Brilo sends to an address your developer gives us, every time a call finishes. Your system receives it and does whatever you want with it: file it, put it in a database, start a job, notify someone. The difference from an action is timing and direction. A webhook fires after the call and only sends data out. An action runs during the call and can bring information back. See Build a custom action.

​
What you would use it for

  • Keeping your own record of every call, in your database rather than in Brilo.
  • Feeding a dashboard or report your team already uses.
  • Starting something in your own system when a call ends, for example creating a job or a ticket.
  • Filing calls into a tool the app store does not cover.
If all you want is a lead in HubSpot or a booking in Google Calendar, use an action instead. Those need no developer. See Connect your tools.

​
What gets sent

The message includes what happened on the call: who called, how long it lasted, how it ended, the summary, the written record, the score, any tags, and the details your agent collected during the conversation. Your developer can see the exact contents in the reference: Post call webhook.

​
What to send your developer

  1. What you want to happen when a call ends, in your own words.
  2. Which system should receive it.
  3. The reference page: Post call webhook.
  4. Your API key, from developer settings in your dashboard.
They will need to provide an address that can receive the message and confirm it arrived. The reference covers how to check a message genuinely came from Brilo, which is worth pointing them at explicitly.

​
FAQ

Yes, with a webhook. Every time a call ends, Brilo sends what happened to an address your developer sets up. It works on every plan, including Free.
A message Brilo sends to another system to say what just happened, for example dropping a call summary into your own database the moment the call ends. Your developer receives it and decides what to do with it.
Yes, and it is usually about an hour of their time. There is nothing for you to configure beyond deciding what you want to happen. See Do I need a developer.
Who called, the length, how the call ended, the summary, the written record, the score, tags, and the details your agent collected. The exact shape is in the post call webhook reference.
Delivery is retried rather than dropped on the first failure. The reference covers the retry behaviour, which is what your developer needs to build against so a brief outage on your side does not lose calls.
No. An integration connects Brilo to a tool it already knows about, with no developer needed. A webhook sends raw call data to whatever you like and needs a developer. Use an integration if one exists for your tool.
No. Webhooks are included on every plan, including Free, which makes them the cheapest way to get Brilo data into your own systems.