Connect WhatsApp to Zapier on the official Cloud API
Point the number's webhook destination at a Zapier catch hook and every incoming message triggers a Zap. Replies go back through the Cloud API with a webhook action. Zapier cannot consume our MCP server, because Zapier is an MCP server rather than a client.
- Incoming messages trigger a Zap
- Official Cloud API, no linked device
- No Zapier app to install
Nothing charged for 7 days. Cancel anytime.
The whole integration is the webhook destination URL, set once per number.
Window after a customer message in which a Zap can reply with free text.
A catch hook to receive and a webhook action to send.
How does an incoming message trigger a Zap?
Start a Zap with the Webhooks by Zapier trigger, choose Catch Hook, and copy the URL Zapier generates. Set that URL as the number's webhook destination and Meta delivers every inbound message to it directly.
The payload gives you the sender, the message content, a timestamp and the message id, which is everything most Zaps branch on. Nothing runs on your infrastructure and there is no Zapier app for us to maintain, because the integration surface is a URL.
The WhatsApp Business app carries on working on the same number throughout, so a person can pick up any conversation the Zap does not handle.
Why does Zapier not use the MCP connector?
Because Zapier runs an MCP server rather than an MCP client. Assistants like Claude and ChatGPT connect into Zapier to use its actions. Zapier does not connect out to a third party MCP server, so it cannot reach ours.
The practical effect is none. MCP is for an assistant to act when a human asks, and a Zap is the opposite shape: something happens, and the automation responds. That is webhook territory in every tool, including ones that do have MCP clients.
If you want an assistant in the loop as well, the connector works in Claude or ChatGPT alongside the Zap rather than inside it.
How does a Zap send a reply?
With a Webhooks by Zapier POST action against the Cloud API, using the number's phone number id and access token from the dashboard.
Timing decides what you are allowed to send. Inside 24 hours of the customer's last message, free text delivers. Outside it, only an approved template does, and this is where most Zaps break in production because testing always happens seconds after a message.
A Zap that handles both needs a path filter on how long ago the last inbound message arrived. It is one extra step and it is the difference between an automation that works on Tuesday afternoon and one that works at three in the morning.
Common mistakes
- Using a Zapier test URL as the destination. It stops listening and messages are delivered to nothing.
- Forgetting Meta's verification GET. The catch hook has to return the challenge before delivery starts.
- Sending free text outside the 24 hour window, which fails silently from the Zap's point of view.
Connect the number at easycoexistence.com, set the webhook destination to your Zapier catch hook, and Zaps start triggering. US$ 9 per number per month, first 7 days free.
Frequently asked questions
Is there an official WhatsApp Zapier app?
You do not need one here. A catch hook receives and a webhook action sends, which keeps you on the official Cloud API without an intermediary.
Can Zapier use your MCP server?
No. Zapier is an MCP server itself and does not act as a client, so it cannot call out to ours.
Does my team lose the phone?
No. Coexistence keeps the WhatsApp Business app working on the same number.
What if my Zap is paused?
Meta retries for a period then stops. Messages still arrive in the app on the phone, so the business loses nothing.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialNothing charged for 7 days. Cancel anytime.Verified on