Integrations: connect Wando with your other tools

Integrations let you connect Wando with the tools you already use. When something important happens in Wando, a notification (webhook) is sent to the platform you choose, to trigger automations.

Supported platforms

• Make (formerly Integromat): visual automations.
• Zapier: connects thousands of apps.
• n8n: self-hosted or open source automation.
• Slack: notifications in your team channels.

Events you can listen to

• New message: when a message comes in from a customer.
• Approved message: when an approved reply is sent.
• Escalated conversation: when a conversation requires special attention.

How to set it up

1. 1Go to the admin panel → Integrations.
2. 2Choose the type (Make, Zapier, n8n or Slack).
3. 3Paste the webhook URL provided by that platform.
4. 4Select the events you want to send and activate it.

What you can and cannot do with a webhook

A webhook is an output: Wando notifies another platform that something happened. It is not an input. It cannot be used for an external tool to send a command to Wando or to modify contacts, tags or campaigns from Zapier. If that is what you are looking for, this feature does not cover it today.

Nor does it replace Meta's official WhatsApp API. Wando's webhook goes from Wando to your automation; the conversation with the customer still lives in Meta's API, which is what you use to send and receive messages.

And it is not guaranteed real time: it is a notification that fires when the event occurs. How long it takes to arrive on the other side depends on the receiving platform, its plan and its load. If your automation needs second-level precision, do not build it on a webhook.

• It works for: notifying, logging, triggering actions in another app, building your own reports.
• It does not work for: writing data into Wando, changing the status of a conversation or replacing Meta's API.

A complete example, end to end

Let's say a veterinary clinic with two locations. It wants every inquiry about an appointment to be logged in a spreadsheet and, if the customer writes outside business hours, for someone on the team to find out in Slack.

Set up two automations. The first: "new message" event to Make. Make takes the data and adds a row in Google Sheets, which is one of the real integrations Wando supports for contacts. The second: "conversation escalated" event to Slack, in the on-call shift channel.

The result: the spreadsheet fills itself and the team doesn't have to watch the dashboard to know there's something pending. Watch out for two things. One, the spreadsheet fills with what you trigger: if you want the actual message time, use the timestamp Meta sends, not the moment the row was inserted. Two, if the volume grows, check the limits of your Make or Zapier plan, because most charge per operation executed.

And if you want to collect payments, Mercado Pago is a separate integration, not a webhook: it connects as a payment, not as an automation.

Common mistakes when setting up the integration

Almost all problems are configuration issues, not Wando. These are the ones that come up most often.

If the automation never triggers, the first thing to check is that the webhook URL is complete and active in the destination platform. Many times the flow was left in draft and never published, and from Wando it looks like nothing arrives.

If it triggers twice, check whether you pasted the same URL into two different integrations with the same events selected.

If it arrives but without the data you expected, the problem is in how you mapped the fields on the Make, Zapier or n8n side. Wando sends the event; what you do with it is up to the other tool.

• Expired webhook URL or one from a draft flow.
• Wrong events selected: you chose one and expected another.
• Two integrations pointing to the same destination.
• Incomplete field mapping on the side of the platform receiving.
• Testing with an event that doesn't exist: if you test "message approved" and nobody approved anything, nothing will arrive.

What to do when something fails

How long it takes to resolve an integration problem varies by case and depends on where the failure is: whether it is on Wando's side, on the receiving platform's side, or on Meta's side. There is no single or guaranteed timeframe.

Before escalating to support, do these three things and write down the result. First, check the execution history in Make, Zapier, or n8n: there you will see whether the webhook arrived and with what response. Second, test the webhook URL with a testing tool to confirm that it responds. Third, verify that the integration is still active in the Wando panel.

Signs that you should escalate: the webhook reaches the platform but with an authentication error, the URL responds correctly from a manual test but not from Wando, or the event appears in the panel and no execution is triggered. With that data, support can locate the problem much faster.

A separate case: if what fails is the approval of a WhatsApp template, that is handled by Meta and the only timeframe that can be stated is up to 48 hours. It is not an integration problem.

How many integrations should you have active

There is no correct number, but there is a criterion: each active webhook is one more thing that can break silently. If nobody looks at the execution history, a failed automation can go unnoticed for weeks.

A reasonable starting point for a small business is one notification integration (Slack, for example) and one logging integration (Make or Zapier to a spreadsheet). That covers the basics: finding out and keeping a record. Only after that should you add more complex automations.

If you have several locations or teams, separate by Slack channel instead of sending everything to just one. And if you use self-hosted n8n, remember that server maintenance is on you: if it goes down, webhooks don't arrive and there's no one to complain to.

Before adding a new integration, ask yourself what concrete decision you're going to make with that information. If the answer is "none, but it's nice to have it," it's probably not worth maintaining.

Integrations, channels and features: don't confuse the three

It's common to mix up these concepts when setting up the configuration. They're kept separate.

Channels are where the conversation comes in and goes out: WhatsApp with Meta's official API, Instagram and Messenger. Integrations are the external tools that receive notifications from Wando: Make, Zapier, n8n and Slack, plus Google Sheets for contacts and Mercado Pago for payments. Features are what already comes inside Wando and doesn't require connecting anything: an inbox with AI suggestions that learns from the business's real replies, templates and campaigns, contacts with tags, statistics, multi-agent, auto-replies by schedule and audio transcription.

The typical confusion is wanting to solve with a webhook something that is already a native feature. For example, building an external automation to reply outside business hours when that's already done with auto-replies by schedule. Before connecting anything, check whether it's already solved inside.

And if what you're looking for is to connect a new channel, that's not done through a webhook: it's done from the channel settings.