conversation.updated

This event exists in the webhook taxonomy but is not currently fired by Insighto. The emission point is intentionally disabled while the platform settles on the right granularity for mid-conversation updates (every assistant turn would be noisy; per-conversation summaries belong on conversation.closed).

Document yourself: do not build production logic that depends on conversation.updated. If you need real-time conversation state, poll the conversations API. If you need closed-state hooks, use conversation.closed.

When it would fire (if enabled)

The intended trigger was: any time a conversation's state, attributes, or metadata changed mid-flight — for example, a new attribute set by the assistant, a status flip, or a human-agent takeover.

Intended payload (for forward-compat)

The shape would mirror the standard envelope:

{
  "id": "evt_01HX...",
  "object": "event",
  "event": "conversation.updated",
  "created_at": "2026-05-14T10:21:33Z",
  "data": {
    "conversation_id": "conv_01HX...",
    "assistant_id": "asst_01HX...",
    "widget_id": "wid_01HX...",
    "contact_id": "cnt_01HX...",
    "attributes": { ... }
  }
}

How to know if/when this turns on

If Insighto enables this in the future, it will be announced in product release notes. Until then, subscribing to conversation.updated simply results in no calls to your endpoint.

Where to next

• conversation.closed — the event you should be building against today.
• captured_form events — real-time form submissions.
• FAQ — webhook quirks and recommendations.