Webhook Events

Conversation control changed event

Fired on Meta's handover protocol (messaging_handovers). WhatsApp: control moves between Meta Business Agent and your app, or the agent is first seen answering a thread; while control.owner is ai_agent, inbound messages arrive on message.received with metadata.standby: true and the agent's replies on message.sent with source: meta_business_agent, and sending any message takes control back. Facebook and Instagram: another app passed you the thread (owner: app) or took or received it (owner: other, with ownerAppId); while you are not the owner, inbound arrive with metadata.standby: true, no automation runs, and sends fail with not_thread_owner. Change control with POST /v1/inbox/conversations/{conversationId}/thread-control. take and request answer 400 platform_not_supported on Instagram Login connections.

postWebhookconversation.control_changed

Payload

testboolean

Always true when present: only a sample sent by POST /v1/webhooks/test with an event carries it. Real deliveries never do.

idstring required

Stable webhook event ID: the dedupe key, also sent as the X-Zernio-Event-Id header and identical on every retry and redelivery. It identifies the event only, never an account or other resource.

event'conversation.control_changed' required

changedAtstring date-time required

timestampstring date-time required

UTC time at which Zernio generated this event (set once when the event payload is built, before delivery is queued). Retries and redeliveries keep the original value, so it reflects the event, not the delivery attempt.

Example payload

{
  "profiles": [
    {
      "externalId": "tenant_42"
    }
  ]
}

Response

Webhook received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.