What is a webhook
A webhook is a mechanism that allows one application to send information to another in real time, as soon as an event occurs. In plain terms: it's like a doorbell that rings in your system when something important happens, instead of having to go ask every couple of minutes if something happened. For example, when someone writes to you on WhatsApp, the platform can notify your server instantly via a webhook.
Why does it matter to an SME?
If you use WhatsApp Business to serve customers, webhooks are the foundation of automation. Without them, your system would have to manually check for new messages, which is slow and unreliable. With a webhook, each incoming message triggers an automatic action: save the contact, notify a salesperson, or even suggest a reply. Understanding this helps you choose your tools better and not get scared when people talk about 'integrations'.
A concrete example
Imagine you have a clothing store and a customer writes to you on WhatsApp at 11:00 PM asking about a size. Without a webhook, the message sits there until someone opens the app. With a webhook, your management system receives the 'message received' event immediately, and can: log the conversation, send an automatic reply saying 'hi, we'll get back to you as soon as we open', and notify the salesperson on duty. All without anyone having to look at the screen.
Common mistakes when using webhooks
- Thinking that a webhook is the same as an API: the API is the door, the webhook is the doorbell that tells you when someone rings.
- Not configuring the URL correctly: if the address where data is sent is not secure or is misspelled, nothing arrives.
- Forgetting that the webhook only sends data: the logic of what to do with that data is up to you (or your software provider).
- Not verifying the webhook signature: anyone could send you fake data if you don't validate that it really comes from WhatsApp.
On platforms like Meta (WhatsApp Business), webhooks are configured in the developer panel, and Meta's official documentation explains the technical details: which events can be received, how to verify the URL, and how to handle retries. Exact sending limits or frequency may vary, so it's always best to consult Meta's official documentation to avoid making up numbers.
If you use a tool like Wando, which connects to WhatsApp's official API, the webhooks are already configured behind the scenes: you don't have to write code, but knowing what they are helps you understand why responses arrive so quickly and why the AI learns from your real responses.
How a webhook is used in practice
Let's consider a real case: an aesthetic clinic in Córdoba that manages appointments via WhatsApp. The owner uses a tool that connects to Meta's official API, and that tool configures the webhook behind the scenes. When a message arrives, the webhook notifies the system instantly, and the system triggers an automatic response: 'Hello! I'll send you the available times.' Then, the team reviews the inbox, approves the AI-suggested replies, and closes the appointment.
The complete flow is: the customer writes → WhatsApp sends the event to the webhook → the platform processes it → the contact is registered and shown in the inbox → an automatic response is sent if applicable. All of this happens in seconds, without anyone watching the screen. If the webhook didn't exist, the message would wait until someone opens the app, and the response would take hours.
What it's confused with and how it differs
The webhook is confused with the API, but they are not the same. The API is the entry door: you request data when you want, like going to the post office to pick up a package. The webhook is the doorbell: it notifies you when something happens, without you having to ask. Both are used together: the webhook notifies you that a message arrived, and then you use the API to request the full content.
It's also confused with a chatbot. The webhook only transports the event; it doesn't decide what to respond. The response logic runs elsewhere, whether it's a programmed bot or an AI system that suggests replies. If someone tells you 'the webhook responded,' they're speaking incorrectly: the webhook only notified.
What happens if you ignore it
If you don't use webhooks, your business stays blind to what happens on WhatsApp. Messages arrive, but your system doesn't know until someone opens the app. That means late responses, customers who leave for the competition, and lost opportunities. In practice, it's like having a store with an 'open' sign but no one at the door: customers come in, look around, and leave.
Moreover, without webhooks you can't automate anything: not saving contacts, not sending automatic responses, not measuring how many messages arrive per day. Tools that use Meta's official API depend on webhooks to function. If you don't configure them, you're paying for an integration that does nothing.
How it relates to Meta's official API
The official WhatsApp API (WhatsApp Cloud API) uses webhooks to notify you of events: incoming messages, delivery confirmations, status changes. Without a webhook, the API is a door that no one knocks on. With the webhook configured, Meta sends a POST to your server every time something relevant happens.
Configuring the webhook in Meta requires verifying your URL with a token, and then choosing which events you want to receive. Meta's official documentation explains the process and retries if something fails. Meta's conversation prices vary by country, so it's always best to review the official documentation so as not to invent numbers.
In tools like Wando, webhooks come pre-configured: you don't have to write code or verify tokens. But knowing how it works helps you understand why responses arrive instantly and why the AI learns from your real responses.
When it does NOT apply or is not advisable
The webhook is not magic: it only works if you have a system that can receive and process the data. If your business doesn't have a CRM, inventory, or management panel, the webhook arrives at an empty place. In that case, it adds nothing until you have a tool that can take advantage of it.
It's also not convenient if you can't keep the URL active. If your server goes down often, events are lost or delayed. Platforms like Meta retry sending, but not forever. And if you don't validate the webhook signature, you expose yourself to fake data. For an SME without a technical team, the most practical thing is to use a platform that already solves it, not try to set it up manually.
Most common mistakes of someone who's just getting the hang of it
The first mistake is thinking the webhook responds on its own. No: it only notifies. The second is believing any URL works: it has to be public, with HTTPS and an endpoint that validates the token. The third is forgetting that the webhook doesn't store anything: if your system is off when the event arrives, you lose it (unless the platform retries).
It's also common to confuse the webhook with a database. The webhook doesn't save messages; it only transports them. And another classic mistake is not checking logs: if something doesn't arrive, the first thing is to see if the webhook was triggered. In tools like Wando, all that is solved, but understanding it saves you frustration when talking to a developer or support.
Frequently asked questions
Is a webhook the same as an API?+
No. An API lets you request data whenever you want (like going to the post office to pick up a package), while a webhook notifies you when something new arrives (like a mailman ringing the doorbell). Both complement each other.
Do I need to know how to code to use a webhook in my business?+
Not necessarily. If you use customer service platforms like Wando, they configure the webhooks for you. But if you want to integrate WhatsApp with your own system, you will need a developer or technical knowledge.
What happens if the webhook fails?+
If the webhook fails, you can lose events (like messages) or receive them late. That's why platforms usually have automatic retries and error logs. In the case of Meta, the official documentation explains how to handle failures and what to do to avoid losing information.
What events can a WhatsApp webhook receive?+
The most common events are: incoming messages, delivery confirmations (blue check), and changes in message status. Meta defines the exact list in its developer documentation, and it may vary depending on the account type.
Can I configure a webhook in Wando without knowing how to code?+
Yes. Wando already has the webhooks configured behind the scenes to connect to the official WhatsApp API. You don't have to touch anything technical: you just use the inbox, templates, and statistics. Knowing what a webhook is helps you understand how it works, but you don't need to write code.
What happens if my server goes down and a webhook arrives?+
Platforms like Meta retry sending several times, but not forever. If your system is down for a long time, you may lose events. That's why it's better to use a cloud-hosted platform that handles retries and error logs for you.
Does the WhatsApp webhook work the same for Instagram or Messenger?+
The logic is the same: Meta uses webhooks to notify events on all its channels. But the configuration may vary depending on the channel and account type. It's best to consult Meta's official documentation for each case.
Can a webhook send WhatsApp messages?+
No. The webhook only receives events (incoming messages, deliveries). To send messages, you use the WhatsApp API. They are two different things: the webhook notifies you, the API lets you reply.