Skip to main content
Webhooks notify your systems whenever a call event occurs. Jelou sends a POST request to the URL you register, which lets you move each call’s outcome into your CRM, your data warehouse, or any internal flow without having to check the log manually. They’re in the Webhooks tab of Voice.
Register a webhook section with the URL field and the Register button, and below it the webhooks table with URL, type, and creation date

Webhooks tab with one registered URL

​
Registering a webhook

You paste your endpoint’s URL into the field and confirm with Register. Jelou will send a POST request to that URL for every call event in your organization. The table below lists the webhooks already registered with three values:
The scope is the whole organization, not a specific agent or number. A webhook registered here receives call events from all your agents.

​
Preparing your endpoint

Your endpoint must accept POST requests with a JSON body and respond quickly. A few considerations that apply to any webhook receiver: Respond before processing. Return a success response as soon as you receive the event and do the heavy work asynchronously. If your endpoint is slow, you risk retries and duplicates. Design for idempotency. The same event can arrive more than once after a temporary failure. Use the call or conversation identifier to recognize what you already processed. Use HTTPS and don’t rely on the URL being secret. The panel exposes no signing secret and documents no verification header, so the URL is the only thing separating your endpoint from the outside. Protect it yourself: use a hard-to-guess path, restrict access by IP if your architecture allows it, and treat everything you receive as untrusted until you validate it against your own data.
If you need cryptographic verification of the origin, confirm it with the Jelou team before building on this webhook: there is no signing mechanism documented on this screen.
Log what you receive. Storing the raw event alongside the response you gave saves a lot of time when something doesn’t add up.
Call events can include conversation and caller data. Treat the endpoint and whatever you store with the same care as any other personal data belonging to your customers.

​
What to do with the events

The end-of-call event is the natural point to close the loop with your systems: recording the outcome of the contact, updating a case status, or triggering the next step of a process. If you’ve defined evaluation criteria and data collection on the agent, that analysis is what turns a call into a usable record: the reason for contact, the classification of the outcome, whether there was a transfer.
Before building the full integration, register an endpoint that just stores the request body and place a test call. Seeing a real event is faster than deducing its shape.

​
From the CLI

jelou voice webhooks

List, inspect, create, and delete webhooks from the terminal, specifying the event type.