What WhatsApp webhook events does Kapso support?

Kapso phone-number webhooks support message received, sent, delivered, read, failed, conversation created, conversation ended, and conversation inactive events.

What is the difference between Kapso webhooks and Meta webhooks?

Kapso webhooks send structured event payloads with filtering, buffering, signatures, retries, and conversation context. Meta webhooks forward the raw Meta payload with an idempotency key for teams that need the exact upstream event.

Can Kapso webhooks trigger AI agents or workflows?

Yes. A webhook can deliver inbound WhatsApp messages to your application, workflow, or AI agent. Project webhooks can also notify your system when a workflow is handed off to a human or fails.

WhatsApp webhooks for messages, statuses, and automations

Receive WhatsApp events your app can trust: inbound messages, delivery status, read receipts, failures, conversation events, and workflow handoffs.

Start building Read webhook docs

What your app can act on

Use webhooks to make WhatsApp state visible to your backend, agent, workflow, CRM, or support queue.

Inbound messages

Receive whatsapp.message.received when a customer messages your number.

Delivery status

Track sent, delivered, read, and failed events after outbound messages.

Conversation events

React when conversations are created, ended, or inactive.

Choose the right webhook surface

Subscribe at the level your integration needs: phone number, raw Meta payload, or project automation.

Kapso WhatsApp webhooks

Structured phone-number events with filtering, signatures, retries, buffering, and conversation context.

Raw Meta webhook forwarding

Raw Meta webhook forwarding gives teams the upstream payload when they need exact Meta fields.

Project webhooks

Project-level events for connection lifecycle and workflow execution, including workflow.execution.handoff.

Production webhook rules

Keep the event loop boring: verify, acknowledge, queue, and route.

Verify the event

Use signed webhooks and idempotency keys before your app mutates state.

Process asynchronously

Acknowledge quickly, then queue work for agents, CRMs, workflows, or support systems.

Escalate deliberately

Route failures, handoffs, and sensitive events to a human-owned path.

Start with one reliable event loop

Connect a WhatsApp number, register a webhook, verify events, and route inbound activity to your app, workflow, or agent.

Start free Receive messages docs