Settings
Webhooks
Automatically receive an event in your own systems as soon as a Leexi call has been transcribed and analyzed.
Definition: A webhook notifies your systems without you having to query Leexi. As soon as a call is transcribed and its AI insights are generated, Leexi sends a request to the URL you configured, along with the call content.
Feature video
No video is available at this time.
Who is this for?
- Technical teams that want to trigger an automatic process at the end of every call.
- Administrators feeding a data warehouse, an internal tool, or a homemade automation.
Permissions and licenses
- Requires: AI Meeting
- Viewing webhooks requires the permission to read webhooks; creating and editing them requires the write permission.
- The data sent follows the public API format: the webhooks reference describes it in detail.
How to use it
Open the Webhooks page
Go to Settings > Advanced > Webhooks. For each webhook, the list shows its name, access rules, URL, description, and status.
Create a webhook
Click "Add", then fill in a name, the URL that will receive the events, and a description. The URL must be reachable from the internet and can only be used by one webhook in your company.
Set the access rules
Three modes are available:
- Linked to a user: the webhook only receives events for calls that user has access to.
- Access to everything: the webhook receives events for every call in the company.
- Custom access: after saving, you are redirected to the Access rules page to define the exact scope.
Handle the events received
Your endpoint receives a POST request for each processed call. Reply with a success code, then process the content on your side. Event, request content and retries: see References › Developer › Webhook events.
Enable or pause a webhook
The switch in the "Active" column pauses event delivery without deleting the configuration, for instance while you run maintenance on your side.
Going further
- Only one event type exists today, sent once the transcript and the AI insights are fully generated. Its content and the retry schedule are detailed in the webhook events reference.
- A webhook whose delivery still fails after ten retries is deactivated automatically: reactivate it once your endpoint is back up.
- API keys cover the opposite need: querying Leexi whenever it suits you rather than waiting for an event.
Frequently asked questions
Any success response is enough. Any error response, like any absence of response, triggers a new attempt.
Because ten consecutive delivery attempts failed. Check that your URL is reachable and answers properly, then reactivate the webhook.
No, the two work independently. An API key remains useful if you want to fetch additional data after receiving an event.
Yes, by configuring custom access and the matching access rules.
Things to watch out for
- The request is not signed: use a URL that is hard to guess and, if you need to validate the data received, call the public API back.
- A slow or unavailable endpoint eventually deactivates the webhook: it is better to acknowledge receipt quickly and process the content afterwards.
- Events are not replayed for the period during which the webhook was inactive: calls processed in the meantime have to be retrieved through the public API.
- The content sent includes the call data: make sure the receiving system offers the level of confidentiality you expect.