Webhook events

Webhooks push events to your own endpoint the moment they happen, so you can act in real time without polling. Ovellan sends three, and each is a plain JSON POST.

The three events

  • lead, a visitor submitted their details through the bot.
  • handover, a visitor asked to talk to a person.
  • conversation, a chat ended (this one fires a few minutes after it goes quiet).
A webhook settings panel with the lead, handover and conversation events selected.
Pick an endpoint and the events to send.

What the payload looks like

Every event is Content-Type: application/json and carries an event_type plus the fields for that event. A captured lead, for example, arrives like this:

A lead just came inevent_type: leadWE POST THIS TO YOUR URL{ "event_type": "lead", "name": "Jane Visitor", "email": "[email protected]", "bot_name": "Support bot", "conversation_link": "https://ovellan.com/…", "captured_at": "2026-07-12T10:00:00.000Z"}
The lead event, as your endpoint receives it.

Two ways to subscribe

The simple way: paste one endpoint URL on your bot's Zapier & webhooks page and it receives all three events. The programmatic way: subscribe per event with the Zapier endpoints, authenticating with your sync key. Either way, we POST the instant an event fires.

The URL is the secret

Payloads are not signed, there is no signature header to verify against. So treat the endpoint URL itself as a secret: serve it over HTTPS and do not expose it anywhere public.

Still need a hand?Email our team and we answer within one business day.
Webhook events | ovellan