Skip to content

Events

The three events evoriqa delivers, with real payloads — and the ones that are deliberately not delivered.

Exactly three events are delivered. Each arrives in the standard envelope described in Webhooks overview; only the data object differs.

lead.created

Fires for every captured lead, whatever the capture path — the widget form, the agent's capture_lead action, or the public lead endpoint.

{
  "id": "9f1c1c2a-1b21-4f7c-9d0f-6a3a4a1c9d55",
  "event": "lead.created",
  "data": {
    "id": "5b3e6c30-9c2c-4a2c-8a53-1f6f0c9a77b1",
    "chatbotId": "0c21f0e4-6d54-4e33-9a2b-7a0f4a2d1c88",
    "email": "sam@example.com",
    "name": "Sam Rivera",
    "phone": null
  },
  "ts": 1786290764000
}

name and phone are null when the visitor did not provide them.

conversation.created

Fires when a new conversation thread starts — on any channel, including the omnichannel ones.

{
  "id": "3d0d1a77-5f2b-4a1e-b6a1-2c8c0f5d9e10",
  "event": "conversation.created",
  "data": {
    "conversationId": "b1d2e3f4-5a6b-4c7d-8e9f-0a1b2c3d4e5f",
    "chatbotId": "0c21f0e4-6d54-4e33-9a2b-7a0f4a2d1c88",
    "source": "public_widget"
  },
  "ts": 1786290801000
}

It fires when the thread is created, not on every message — see the note below.

csat.received

Fires when a visitor submits a satisfaction rating, on their first rating for that conversation.

{
  "id": "7c9b0a52-2f38-4b6d-a0e1-9f3b7d4c2a61",
  "event": "csat.received",
  "data": {
    "conversationId": "b1d2e3f4-5a6b-4c7d-8e9f-0a1b2c3d4e5f",
    "rating": 5,
    "comment": "Answered instantly, great."
  },
  "ts": 1786291042000
}

rating is 1–5. comment is null when none was written.

What is not delivered

Note:

Per-message, handoff, and action-run events are not available. They are on the roadmap, deliberately deferred — per-message would be too high-volume to fan out, and handoff has several entry points that need unifying first.

Only events the platform genuinely emits are offered, so subscribing to something and hearing nothing always means "nothing happened", never "that event does not exist".

If you need to react to a message or a handoff today, poll the v1 conversations endpoint, or work from the Inbox notifications instead.

Where to go next

Last updated