Connect WhatsApp to Make on the official Cloud API
Point the number's webhook destination at a Make custom webhook and every incoming message starts a scenario. Replies go back through the Cloud API with an HTTP module. Make cannot use our MCP server, because Make is an MCP server itself rather than a client.
- Incoming messages trigger a scenario
- Official Cloud API, no linked device
- The team keeps the app on the phone
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 scenario can reply with free text.
A custom webhook to receive and an HTTP module to send. Nothing to install.
How does a WhatsApp message start a Make scenario?
Create a custom webhook module in Make, copy the URL it gives you, and set it as the number's webhook destination. From then on Meta delivers every message sent to the number straight to that URL as an HTTP POST, and the scenario runs.
The payload carries the sender, the message body or a media reference, a timestamp and the message id. From there it is an ordinary scenario: route on the content, look the customer up, call whatever else you run.
Because this is Coexistence, the same message is also in the WhatsApp Business app on the phone. A person can answer it, the scenario sees what they sent, and neither ends up replying on top of the other.
Why can Make not use the MCP connector?
Because Make is an MCP server, not an MCP client. It exposes its own scenarios to assistants like Claude and ChatGPT, which connect inward to Make. It does not connect outward to somebody else's MCP server.
That direction is the whole story. Our connector is a server waiting to be called, and Make has nothing that calls out to one, so the two never meet. This is different from n8n, which has an MCP Client Tool node and can consume a remote server over OAuth.
It costs nothing in practice. The webhook path does everything a scenario needs, and it is the path that reacts to incoming messages, which MCP cannot do in any tool.
How does a scenario send a reply?
With an HTTP module against the Cloud API, using the number's phone number id and access token. Both are readable from the dashboard, or through the MCP connector if you would rather an assistant fetch them for you.
What to send depends on timing. Inside 24 hours of the customer's last message, free text works. Outside it, only a template Meta has approved will deliver, and a scenario that only ever sends free text will go quiet on the first overnight case.
The durable shape is a router: check how long ago the last inbound message arrived, and take the free text branch or the template branch accordingly.
Common mistakes
- Leaving the webhook pointed at a Make URL from a scenario that is off. Meta delivers to it and nothing runs.
- Not answering Meta's verification request. Meta sends a GET with a challenge before delivering anything.
- Replying with free text outside the 24 hour window. It fails, and from the scenario's point of view it looks like nothing happened.
Connect the number at easycoexistence.com, set the webhook destination to your Make custom webhook, and scenarios start receiving. US$ 9 per number per month, first 7 days free.
Frequently asked questions
Can Make connect to your MCP server?
No. Make is an MCP server rather than a client, so it has no way to call out to ours. The webhook path covers everything a scenario needs.
Do I need a Make app for WhatsApp?
No. A custom webhook receives and an HTTP module sends. The integration is a URL and a REST call.
Can the team still answer from the phone?
Yes. That is what Coexistence means. The app keeps working on the same number and the scenario sees what the human sent.
Can one scenario serve several clients?
Yes. Point every number at the same webhook and route on the receiving phone number id in the payload.
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