How Webhooks Power WhatsApp Automation

What Is a Webhook?

A webhook is an HTTP callback. When a specific event occurs — like a WhatsApp message being received — the API sends an HTTP POST request to a URL you've configured in advance. Your server receives the JSON payload, processes it, and responds.

Unlike polling (where your server asks the API every N seconds "any new messages?"), webhooks are event-driven. Events arrive in real time — typically within 1–2 seconds of the trigger. This makes webhooks the only practical approach for building responsive chatbots, live inbox UIs, or instant notification systems.

WhatsApp Webhook Event Types

• messages — a new inbound message from a customer (text, image, document, voice note, etc.)
• message_status — delivery receipts: sent, delivered, read, or failed
• template_status — a message template was approved, rejected, or paused by Meta
• account_alerts — quality rating changes or messaging limit tier updates
• phone_number_quality — your WABA's phone number quality rating has changed

How WasapFlow Bridge Delivers Webhooks

WasapFlow Bridge acts as a relay between Meta's Cloud API and your application. When Meta fires a webhook event to our system, we forward it to your configured webhook URL within milliseconds — with a consistent, normalized payload format across all event types.

Our webhooks include an HMAC-SHA256 signature in the X-Hub-Signature-256 header. This allows your backend to verify that the payload genuinely came from WasapFlow and hasn't been tampered with in transit. Always verify this signature before processing any incoming webhook payload.

Common Automation Use Cases

• Auto-reply chatbot: When a customer sends "Hi", trigger an automated greeting with a product menu.
• Order updates: When your backend processes an order, send a template message to the customer's WhatsApp automatically.
• Support ticketing: Route incoming WhatsApp messages to your helpdesk system and assign to the right agent.
• Lead qualification: Run a conversational intake form via WhatsApp — capture answers and pass them to your CRM.
• Re-engagement: When a customer hasn't replied in 24 hours, trigger a follow-up template message to continue the conversation.
• Payment notifications: Fire a WhatsApp message when an invoice is paid, a subscription renews, or a payment fails.

Implementation Tips

Your webhook endpoint must respond with HTTP 200 within 20 seconds. If it doesn't, the delivery will be retried. Build your handler to respond quickly and do heavy processing asynchronously — receive the event, push it to a queue, return 200, then process from the queue.

Make your handler idempotent — Meta may occasionally deliver the same event more than once due to retries. Use the message_id field as a deduplication key and skip reprocessing events you've already handled.

For local development, use a tunneling tool like ngrok or Cloudflare Tunnel to expose your local server for webhook testing before deploying to production.