Chatwoot Agent Bot Webhook
Receives Chatwoot Agent Bot webhook events for the channel. Chatwoot owns the messaging inbox (Facebook, website widget, and others). This Agent replies through the Chatwoot API and maps native bot handoff to conversation pause/resume. Requests are verified via the X-Chatwoot-Signature HMAC-SHA256 header using the configured webhook secret unless an api_key is present and no secret is set. The route acknowledges immediately (Chatwoot times out in about 5 seconds) and processes events asynchronously.
Path parameters
Headers
sha256= plus hex HMAC-SHA256 of {timestamp}.{rawBody} keyed with the Agent Bot webhook secret. Required when the webhook URL does not include an api_key, and whenever a webhook secret is configured.
Request
Chatwoot event name. Incoming visitor messages use message_created. Staff takeover and assignment use conversation events such as conversation_opened, conversation_status_changed, and conversation_updated.
Message id on message_* events. Conversation display id on conversation_* events.
Incoming visitor messages are incoming (or 0). Staff replies are outgoing (or 1).
When true, the Agent ignores the message (Chatwoot private note).
Nested on message events. Conversation events send id, status, and meta at the top level instead.
Top-level conversation status on conversation events.
Top-level conversation meta on conversation events.