Skip to content

Guides

Using a WhatsApp Webhook for Incoming Messages with whatsappx.si

Learn how to use whatsappx.si outbound webhooks to forward incoming WhatsApp messages to your own server for custom automation and workflows.

On this page

TL;DR

  • A WhatsApp webhook acts as a bridge that automatically pushes incoming message data from your inbox to your own server or application.
  • whatsappx.si provides outbound webhooks that send incoming message payloads to a specified URL, secured by a shared-token header.
  • Developers can use this data to trigger external workflows, update internal databases, or integrate with custom software solutions.
  • Detailed technical specifications and payload structures are available in the public documentation.

What is a webhook for incoming WhatsApp messages?

A webhook for incoming WhatsApp messages is an automated notification system that sends data from your messaging platform to a custom URL whenever a new message arrives. Instead of manually polling for data, your server listens for these "pushes," allowing your systems to react in real-time to customer inquiries.

By using a webhook, you can move beyond the standard shared inbox experience. When a customer sends a message to your WhatsApp number, the platform instantly sends a POST request containing the message details—such as the sender's phone number, the message content, and the timestamp—to the destination you define. This allows businesses to build custom integrations that trigger specific actions without needing to manually copy data between platforms.

How do outbound webhooks work in whatsappx.si?

Outbound webhooks in whatsappx.si forward incoming messages to your own server URL using a secure, shared-token header for authentication. When you configure your webhook settings within the platform, you provide a destination URL where you want the message data to be sent.

Every time a message is received, whatsappx.si generates a payload and transmits it to your endpoint. To ensure that the requests are coming from your authorized workspace, the platform includes a shared-token header in the request. Your server can verify this token to confirm the authenticity of the data before processing it. This ensures that your internal systems only react to verified information originating from your linked WhatsApp number. You can find the full technical requirements and expected payload structures in our public API docs.

What can you build with a WhatsApp webhook?

With a webhook, you can create custom workflows that connect your WhatsApp conversations to your existing tech stack. Since whatsappx.si does not include built-in CRM integrations, webhooks are the primary method for developers to create these connections.

For example, a clinic could use a webhook to automatically log appointment inquiries into a custom patient management system as soon as a message is received. Another example is a logistics company that might trigger an automated status update in their backend database whenever a customer sends a tracking request. By processing these webhooks, you can build custom notification systems, sync data with your internal tools, or trigger alerts in other software applications based on specific keywords or customer interactions.

How to get started with API and webhooks

To start using webhooks, you first need to connect your WhatsApp number to the platform by scanning the QR code, which enables the shared inbox functionality. Once your workspace is active, you can access the developer settings to define your webhook URL and generate the necessary API keys.

It is important to remember that whatsappx.si provides the software for these connections; however, you are responsible for building and maintaining the server-side logic that receives and processes the webhook data. If you are looking to integrate your messaging with custom business logic, our API and webhooks feature provides the flexibility needed to build exactly what your team requires. For more information on how to manage your team and communication channels, you can explore our shared inbox guide.

Important considerations for webhook security

When implementing webhooks, security and data integrity should remain a priority. Because whatsappx.si handles data through these integrations, you must ensure your receiving server is configured with HTTPS to encrypt the incoming payload.

Additionally, always validate the shared-token header to prevent unauthorized requests from interacting with your system. While our platform provides the infrastructure to forward the data, the security of the data after it reaches your server is under your control. By following standard security practices, you can safely utilize incoming message data to power your custom internal tools and automate your business operations effectively.

Frequently asked questions

What is a shared-token header in whatsappx.si webhooks?
The shared-token header is a security mechanism used to verify that the incoming webhook request is originating from your whatsappx.si workspace. By checking this token on your server, you can ensure that your system only processes legitimate data sent by your configured webhook.
Can I use webhooks to build a customer chatbot?
whatsappx.si does not offer a chatbot. While you can use webhooks to receive data on your own server, the platform itself is designed as a shared inbox and AI assistant for teams. You must build your own logic if you intend to automate replies via your own infrastructure.
Does whatsappx.si provide built-in CRM integrations?
No, whatsappx.si does not have built-in CRM integrations. Instead, we provide a REST API and outbound webhooks, which allow developers to connect their own CRM or internal tools to the platform to sync data and manage conversations programmatically.
Where can I find the documentation for webhooks?
You can find all technical details, including payload examples and authentication requirements, in our public API documentation at /docs. This resource is designed for developers looking to integrate their own systems with whatsappx.si.