May 13, 2026
Customer webhook notifications
Subscribe to conversation.started, conversation.ended, and message.received events. Configure an HTTPS endpoint per bot from the bot settings page.
Subscribe to conversation.started, conversation.ended, and message.received events. Configure an HTTPS endpoint per bot from the bot settings page.
Your bot can now push events to your backend in real time. Configure an HTTPS endpoint per bot under Settings → Webhooks, and we'll POST a signed JSON payload whenever:
conversation.started — a visitor opens a new threadmessage.received — a visitor sends a messageconversation.ended — a thread goes idle for 30 minutesPayloads are signed with HMAC-SHA256 so you can verify they came from us. We retry failed deliveries up to 3 times with exponential backoff.
Useful for piping conversations into your CRM, triggering follow-up emails, or logging to your own analytics stack.
Commit: 5b76816