Updated on October 25, 2026
Make and Zapier connect to the official WhatsApp Business API through ready-made apps: on Make, the WhatsApp Business Cloud app; on Zapier, the WhatsApp Business app (not to be confused with “WhatsApp Notifications”). Both send free-form messages, templates and media and start a workflow when a message arrives. When the ready-made app isn’t enough, or when you use an API provider, the route is the same on both tools: receive Meta’s webhook at your own URL and send through the HTTP module.
This guide shows what each app offers, the requirements on Meta’s side, the limits that catch people off guard and an example automation built on the webhook route.
What you need before you start
Any automation on the official API relies on the same Meta setup:
- a Meta business portfolio;
- a WhatsApp Business Account (WABA) with a number registered on the Cloud API;
- an approved display name;
- approved templates to start conversations;
- a payment method for billable messages.
And two rules no automation tool changes:
- Free-form messages only inside the 24-hour window. Text, images or documents without a template can only be sent if the customer wrote to you in the last 24 hours. Otherwise, templates only.
- Opt-in. Meta’s policy requires the customer’s permission to receive messages from the business.
Make: WhatsApp Business Cloud app
Make’s documentation lists these modules in the WhatsApp Business Cloud app:
| Type | Modules |
|---|---|
| Instant trigger | Watch Events |
| Messages | Send a Message, Send a Template Message |
| Media | Upload a Media, Download a Media |
| Phone number | Register a Sender, Verify a Sender, Deregister a Sender, Enable Two-Step Verification |
| Profile | Get a Business Profile, Update a Business Profile |
Connection. According to the app page, the current connection asks you to choose a signup mode, the business portfolio and the WABA, and generates the token automatically, with no developer account required. The regular mode is recommended; there’s also a coexistence mode for numbers already on the WhatsApp Business app, which isn’t available in every country. The older WhatsApp Business Cloud (legacy) connection asks for a permanent system user token and the WABA ID, and Make says it supports it only until April 2027. If you still use the legacy connection, generate the token following the permanent token guide and plan the switch.
Watch Events. A webhook-based trigger: you create the webhook inside the module, pick the connection and tick the events. Leaving all of them unticked receives every type.
New numbers. Make points out that Meta can take up to one business day to review the business and display name, and that during that time the number can only send a few business-initiated test messages.
Zapier: WhatsApp Business app
Zapier has two apps with WhatsApp in the name. The one that uses your own WABA is WhatsApp Business; WhatsApp Notifications is a separate integration. According to Zapier’s help center:
| Type | Name |
|---|---|
| Trigger | New Message Received |
| Trigger | New Message Status Updated (sent, delivered, read, failed) |
| Search | Get Attachment (downloads media by media ID) |
| Action | Send Freeform Message |
| Action | Send Media Message |
| Action | Send Template Message |
Points Zapier itself documents:
- Premium app. Available on the paid Professional, Team and Enterprise plans, not on the Free plan.
- Connection. You log in with your Meta account, pick the business profile and the WABA number, and grant Zapier access.
- Silent failures. A Zap run may show as successful even when the message wasn’t sent. Use the status trigger to record failures.
- Number format. Numbers must be in international format (country code + area code + number).
Limits that catch people off guard
| Situation | What happens | How to avoid it |
|---|---|---|
| Free-form action to someone who hasn’t written | Meta rejects the send outside the 24-hour window | Use the template action |
| Template parameters out of order | Meta parameter error | Map variables in the same order as the template |
| Large list in a single scenario | Volume hits the portfolio messaging limit | Spread it over several days |
| Marketing message not delivered | Per-user marketing limit (131049) | Don’t resend within 24 hours |
| “Successful” Zap with no delivery | Failure only shows in the status | Handle the failed status trigger |
The cost doesn’t change with the tool either: Meta charges per delivered message, based on its category (marketing, utility, authentication or service). See how much a WhatsApp campaign costs to estimate it.
Alternative: webhook + HTTP (works with any provider)
Ready-made apps connect straight to Meta. If you use an API provider, need an operation the app doesn’t have (interactive lists, mark as read, Flows) or want the same event in several systems, use the generic modules:
| Function | Make | Zapier |
|---|---|---|
| Receive events | Webhooks > Custom webhook | Webhooks by Zapier > Catch Hook |
| Reply to the caller | Webhooks > Webhook Response | Fixed 200 response, not customizable |
| Send a message | HTTP > Make a request | Webhooks by Zapier (POST or Custom Request action) |
| Max event size | 5 MB | 10 MB on Catch Hook, 2 MB on Catch Raw Hook |
Sources: Webhooks on Make and webhooks on Zapier. On Zapier, Webhooks by Zapier is also a premium app.
Two details matter:
- Meta verification. If the URL will be registered directly on a Meta app, it must return
hub.challengeon theGETverification. On Make, the Webhook Response module handles that. On Zapier, Catch Hook returns a fixed response and won’t pass this verification. - Fast response. Make returns “200 Accepted” when the scenario has no Webhook Response, and Zapier always returns 200. That’s good: the event source doesn’t wait for the scenario to finish.
Make example: a form lead gets a template
A common scenario: a website form sends the lead to Make, which sends a welcome template.
- Custom webhook receives the form data (name, phone, interest).
- Tools > Set variable (or a function) cleans the phone number into international format without
+. - HTTP > Make a request sends the template:
{
"messaging_product": "whatsapp",
"to": "{{phone}}",
"type": "template",
"template": {
"name": "lead_welcome",
"language": { "code": "en_US" },
"components": [
{ "type": "body", "parameters": [{ "type": "text", "text": "{{name}}" }] }
]
}
}- A second scenario, with another Custom webhook, receives statuses and writes
failedones to a spreadsheet or CRM. Common error codes are covered in WhatsApp API errors, and the status format in message status via webhook.
Since the form records the lead’s consent, sending the template meets the opt-in rule. Store the accepted text and the date.
How to do it with Vectalk
Vectalk receives Meta’s events and forwards the same payload to the URLs you register, and accepts the same send JSON as the Cloud API. On Make and Zapier, that means using the webhook + HTTP route:
- Copy the URL of the Custom webhook (Make) or Catch Hook (Zapier).
- Register it with
POST https://apis.vectalk.com.br/api/webhooks, passinginstance_id,urlandname. You can register several URLs on the same instance, and all of them receive the same event. - In the HTTP module, send to
POST https://apis.vectalk.com.br/api/messageswith the headerAuthorization: Bearer YOUR_TOKENand the JSON body from the example above. With an instance token, the number is resolved automatically.
curl -X POST https://apis.vectalk.com.br/api/webhooks \
-H "Authorization: Bearer $VECTALK_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"instance_id": "YOUR_INSTANCE_ID",
"url": "https://hook.make.com/YOUR_WEBHOOK",
"name": "Make"
}'Vectalk expects a 200 response within 20 seconds, which Make and Zapier already do by default. See webhooks and sending templates in the docs (in Portuguese). Message costs come on your Vectalk invoice, with no card at Meta. Create your account at apps.vectalk.com.br/register.
If you prefer a self-hosted tool with more control over code, see n8n with the official API.
Frequently asked questions
Make or Zapier: which is better for WhatsApp?
It depends on what you need. Make’s app also covers media upload, number registration and business profile, and Webhook Response can answer Meta’s verification. Zapier’s app has a ready-made status trigger and is simple to connect, but it’s premium. If you use an API provider, both work the same way through webhook + HTTP.
Can I use Make or Zapier with WhatsApp via QR code?
Both platforms’ official apps use the official API. QR code integrations rely on unofficial APIs, which go against WhatsApp’s Terms of Service. See official vs. unofficial API.
Why does my Zap show success but the message never arrived?
Zapier documents that a run may show as successful even when the send fails. The real cause shows up in the failed status, with Meta’s error code. Use the status trigger to record those failures.
Can I send bulk messages through Make or Zapier?
You can iterate over a list and send a template to each contact, but Meta’s limits still apply: portfolio messaging limits, per-user marketing limits and opt-in rules.
Official sources consulted on October 25, 2026: Make: WhatsApp Business Cloud, Make: WhatsApp Business Cloud modules, Make: Webhooks, Zapier: WhatsApp Business, Zapier: Trigger Zaps from webhooks, Meta: Get opt-in for WhatsApp, Vectalk docs: Webhooks.