Connecting WhatsApp to Zapier, Make and other automation tools
The honest answer, and why it is more useful than a connector list would be.
There is no one-click Zapier, Make or n8n connector, and it would be dishonest to imply otherwise. What exists is a general mechanism that any of those tools can drive, plus a step inside your flows that can call them back.
That is less convenient than a listing in an app directory and, in practice, more capable — because it works with any tool that can send a web request, including the one you already pay for.
The two directions
| Your tool starts a WhatsApp flow | A WhatsApp flow calls your tool | |
|---|---|---|
| What happens | Something occurs elsewhere; a customer gets messaged | Mid-conversation, the flow fetches or sends something |
| Set up in | Your automation tool | The flow builder |
| Needs | Your account API key | A web address your tool provides |
| Good for | "When a form is submitted, message them" | "When they ask, look it up" |
Most useful setups are the first. Something happens in a spreadsheet, a form, a booking system or a CRM, your automation tool notices, and a WhatsApp flow runs.
What it looks like in practice
Say a customer fills in a form on your website and you want them to get a WhatsApp message with what happens next.
- In your automation tool, the form submission is the trigger.
- Add an action that sends a web request — every one of these tools has one, usually called something like "Webhook" or "HTTP request".
- Point it at us, using your account API key so we know it is you.
- Include two things: a short event name you have chosen, and the customer's phone number in full international format.
- In the flow builder, build a flow that starts on that event name.
Steps one and two are things your tool already does. Steps four and five are the only parts specific to WhatsApp, and neither needs code.
What to hand whoever set up your automations
If somebody else maintains your Zaps or scenarios, this is the whole brief:
- Send a POST request to
/api/external/eventon our domain. - Authenticate with the account API key from Settings, sent as
the
X-API-Keyheader. - Body: a JSON object with
event(the name you agreed) andphone(full international format). Any other fields the message needs can go alongside. - Optionally include an
event_id— if the request is retried with the same id, it is recognised as a duplicate rather than messaging the customer twice.
That is one action in one automation. If the person quotes you a project, they have misunderstood the scope.
The rule this does not bend
Your automation tool cannot create permission to message somebody. A flow started this way still reaches a chat that is almost certainly outside the 24-hour customer service window, so it needs an approved template, per Meta's sending messages documentation and its template documentation.
Which means the template is the long pole, not the integration. Submit it first, because approval takes time and the connection itself takes minutes.
Calling your tool from inside a flow
The other direction. Most of these platforms can give you a web address that runs a scenario when something calls it, and the flow builder has a step that calls a web address mid-conversation.
So a customer answering a question can cause a row to be added somewhere, a ticket to be created, or a notification to be sent — without leaving the conversation. The step branches on success and failure, and the failure path is not optional; details in calling your own system from a flow.
When you do not need any of this
Worth checking before you build, because two common cases are already covered:
- Shopify. Connected directly. Do not route Shopify orders through a third-party tool to reach WhatsApp — you would be adding a moving part between two systems that already talk.
- A spreadsheet. Google Sheets connects directly too, both for looking values up mid-flow and as a place to write answers. See WhatsApp automation with Google Sheets.
Reach for a general automation tool when the thing you care about lives somewhere neither of those covers.
What it costs
Nothing on our side — the connection is part of your plan. You pay for whatever your automation tool charges, and for the WhatsApp messages the flow sends. A flow that reaches a cold chat sends a template, which is billed; a flow that answers somebody who messaged you first is free and unlimited under Meta's pricing documentation.
Frequently asked
Is there an official app in Zapier's directory?
No. The web-request action is the route, and it works in every tool of this kind.
Which tool should I use?
Whichever you already have. None of them is better at this particular job, because all of them are just sending one request.
Can I trigger a flow for many customers at once?
Each request is one customer. For messaging a list, use a broadcast — that is what it is for.
Can my tool read my WhatsApp conversations?
Not through this. For reading conversations and building automations conversationally, the Claude connection is the route — see connecting Claude to your WhatsApp account.
Five things worth wiring up
Not exhaustive, but these are the ones small businesses build first and get value from immediately:
- A website form — someone enquires, they get a WhatsApp acknowledgement with what happens next.
- A booking system — an appointment is made, they get a confirmation, and a reminder the day before.
- An invoicing tool — an invoice goes overdue, they get a polite nudge.
- A spreadsheet row — somebody adds a row, a customer gets messaged.
- A helpdesk ticket — a ticket is resolved, the customer hears about it where they actually read things.
Each is one trigger and one action in a tool you already use, plus one flow at this end. Start with whichever of those causes the most "did anyone tell the customer?" in your business.
Two things to get right
| Detail | Why it matters |
|---|---|
| Phone number format | Full international format, or the flow has nobody to message |
| A specific event name | A flow with no event name runs on every event your tools send |
That second row is worth being firm about. If your booking tool and your invoicing tool both post events, and one of the flows was left without a name, an appointment reminder will go out when an invoice goes overdue.
Volume, before you switch it on
Ask how many messages the new connection would produce on a busy day, and check it against your messaging limit. That limit is a pool at the account level, starting at 250 unique recipients per rolling 24 hours and climbing 250 → 2,000 → 10,000 → 100,000 → unlimited per Meta's messaging limits documentation.
An integration that quietly exceeds your tier will look like an integration that half-works. Better to know the number before you connect it than to debug it afterwards.
Keeping it working
Connections built this way fail quietly, in three ways worth knowing about before they happen:
- The API key was rotated and the automation still sends the old one. Every request then fails as unauthorised.
- The flow was unpublished or renamed, so events arrive and nothing is listening.
- The other tool's account changed hands, and whoever owns it now does not know what the Zap does.
None of those produce a complaint from a customer, because the customer simply never hears from you. Add this connection to whatever quarterly check you already run — see keeping your integrations working.
The short version
Worth saying once more, because it is the thing people arrive looking for: the absence of a directory listing is not the absence of an integration. It is the absence of somebody having pre-filled the form for you, and the form has four fields.
No connector, one general mechanism, and it works with whichever tool you already pay for. Your tool sends one web request with your API key, an event name and a phone number; a flow starts on that event name. Get the template approved first, use a specific event name, and check the volume against your messaging limit before you switch it on.
Common questions
Do I need a developer?
Not if you already build automations in one of these tools — it is one more action of a kind you have used before. If you have never built one, the tool's own help is the place to start rather than this page.
Where do I find my API key?
In your settings. Treat it as a password: it lets anything holding it start flows in your account, so rotate it if it has been shared around.
Can I test it before it reaches customers?
Yes — send the request with your own phone number and watch the flow run. That is the whole test, and it takes a minute.
What happens if my tool sends the same event twice?
If it includes the same reference on both, the second is recognised as a duplicate. Without one, the customer gets two messages.