Send conversation events to your systems.

Choose the events you need. Breezaro posts signed JSON to your HTTPS endpoint, where your CRM, automation, or internal service can use it.

Explore plansRead the webhook guide

Available on Standard and above, or during an active trial, when Webhooks are enabled for your assistant. Endpoint limits depend on your plan.

BreezaroSigned JSON POSTYour HTTPS endpoint
Illustrative conversation.started payload
{
  "id": "evt_2b6f7e3a-9c9b-4a91-8ce1-7b6dcd6db8a2",
  "type": "conversation.started",
  "createdAt": "2026-07-29T14:03:11.482Z",
  "apiVersion": "2026-07-29",
  "data": {
    "conversation": {
      "id": "sample-conversation",
      "source": "widget"
    },
    "startedAt": "2026-07-29T14:03:11.482Z",
    "visitor": { "language": "en" }
  }
}
Signed headerswebhook-id · webhook-timestamp · webhook-signature

Choose what matters to your workflow.

Subscribe each endpoint to the conversation events your system needs. Each event includes a type, an id, a timestamp, and its own data.

Events identify their source, such as the web widget, WhatsApp, Messenger, or Instagram. Which events occur depends on the channel and action.

  • A conversation begins or a message is saved

    React to new conversations and messages from visitors, the assistant, or operators. For a connected channel, a saved bot reply does not yet prove that the provider delivered it.

    conversation.startedmessage.created

  • A person is requested or joins the conversation

    Track an assistant's request for an operator and an operator's takeover. A takeover can also happen without an earlier request.

    handover.requestedhandover.claimed

  • A custom action finishes running

    Read-only actions can run in the web widget or a connected channel. Confirmed data-changing actions currently run in the web widget. The event reports the outcome and limited arguments, never your API's response.

    custom_action.readcustom_action.executed

  • A visitor is verified

    Use an identity-verification event to update a customer record. It can contain contact details; the available fields depend on the verification method and channel.

    visitor.verified

From selected event to your endpoint.

Configure Webhooks in the dashboard and test the same delivery path used for live events before you use them in an automation.

See the setup and payload guide

  1. Add an HTTPS endpoint

    Enter your receiving URL and select at least one event type. You can edit the selection later.

  2. Send samples

    The dashboard queues one sample for each selected event. Each has test: true, so your receiver can keep test data out of live workflows.

  3. Verify the signature

    Check webhook-id, webhook-timestamp, and webhook-signature against the exact request body before trusting the event.

  4. Inspect deliveries

    See recent statuses, response codes, and attempts in the dashboard. A settled delivery can be sent again while its payload is retained.

A clear record when an endpoint responds or fails.

Events are queued and sent in the background. Your endpoint confirms success with a 2xx response; the dashboard shows the outcome of each delivery.

Retryable failures are attempted again
Breezaro makes up to eight attempts with increasing delays for retryable failures. Your endpoint has ten seconds to respond.
Review or resend a delivery
Recent delivery records remain for 30 days and payload bodies for seven days. After 20 consecutive failed events, an endpoint is disabled and the dashboard shows a notification.
Handle duplicates and busy endpoints
Events can arrive more than once or out of order, so deduplicate by event id. When an endpoint already has 1,000 pending deliveries, new events for it are dropped until the backlog clears.

How do Webhooks fit with Custom Actions?

The two features connect different parts of a conversation to your systems.

Explore Custom Actions
Will a webhook call my booking or order API?
A webhook reports that something happened in Breezaro. Custom Actions are what let the assistant call an API during a conversation, such as looking up an order or creating a booking after confirmation.
Do the same events fire on every channel?
Conversation and message events can come from the web widget and connected channels. Some event types depend on the channel: confirmed data-changing Custom Actions currently run only in the web widget.
Do I need to run my own server?
You can use an automation tool that provides an HTTPS webhook URL. If that tool does not verify the signature, protect the URL as a secret; use your own receiver if signature verification is required for the next action.
Which plan includes Webhooks?
Standard and higher plans, and active trials, qualify when Webhooks are enabled for the assistant. Your plan determines the endpoint limit. Webhook deliveries do not use chat credits.

Put conversation events to work.

Start with one event and one endpoint, then add only the signals your workflow uses.

Explore plans