More than 3 billion people use WhatsApp every month. One of them may be messaging your business right now. And someone on your team is copying that person’s details into a spreadsheet by hand.
Meta’s CEO shared that number on the company’s Q1 2025 earnings call. Your customers are already on WhatsApp. The question is how fast your systems can keep up.
Connecting WhatsApp API with Zapier or Make fixes that. You can send new chats to your CRM, Google Sheets, or email. You can send replies and order updates without typing them. You do not need to write code.
This guide shows you how, step by step. It also covers the rules and costs that trip up most beginners.
Last updated: November 11, 2026. Facts checked against Zapier, Make, and Meta documentation on this date.
Quick answer: How do you connect WhatsApp API with Zapier or Make?
- Get a WhatsApp Business Account (WABA) with a registered business phone number and an approved display name.
- In Zapier, use the WhatsApp Business app. It needs a paid Zapier plan. In Make, use the WhatsApp Business Cloud app.
- Log in and pick your business number.
- Choose a trigger, like a new message received.
- Add an action, like adding a row to a sheet or sending a template message.
- Test it, then turn it on.
Key rule: Outside a 24-hour window, you can only send approved template messages. More on this below.
What does it mean to connect WhatsApp API with Zapier or Make?
It means linking your WhatsApp Business number to an automation tool. The tool listens for an event, like a new message. Then it runs actions in other apps. It can also send WhatsApp messages for you.
This uses the WhatsApp Business Platform, not the normal WhatsApp app on your phone. Zapier’s WhatsApp Business app connects to Meta’s Cloud API through a login step. Make’s WhatsApp Business Cloud app works with the same Cloud API.
Here is what that looks like in real life:
- A customer messages you. A new lead appears in your sheet.
- A shopper fills a form. They get a WhatsApp template message.
- A message fails to deliver. Your team gets an alert.
Zapier’s site says it connects with 9,000+ app integrations. Make’s site says it has 3,000+ native apps. Either way, your WhatsApp number can reach most of the tools you already use.
What you need before you start
Get these ready first. It saves hours later.
For Zapier’s WhatsApp Business app, Zapier lists these requirements:
- A paid Zapier account. WhatsApp Business is a premium app, so the Free plan does not include it.
- A Meta Business Manager account.
- A WhatsApp Business Account with a valid, registered phone number. A personal WhatsApp number will not work.
- An approved display name. Zapier cannot fix display name problems for you.
- Opt-in consent from each person you plan to message.
For Make, you need a Make account and a WhatsApp Business Cloud API setup from Meta. Make’s WhatsApp Business Cloud app has Watch Events, Send a Message, and Send a Template Message modules.
Also have ready:
- A message template, approved by Meta, for first contact
- A clear goal, like “log every new chat in a sheet”
- A test phone to send messages from
Not sure a sheet is enough? If you want WhatsApp inside a full CRM, read our guide on how to connect WhatsApp API with your CRM first. It compares the main methods, so you can pick the right path before you build.
Zapier vs Make: which one should you pick?
Both tools work. They suit different needs.
| Feature | Zapier | Make |
|---|---|---|
| WhatsApp app | WhatsApp Business (connects to Meta’s Cloud API) | WhatsApp Business Cloud |
| Plan needed | Paid plan (Professional, Team, or Enterprise) | Free plan available. Check the app page for your setup. |
| Incoming message | Trigger: New Message Received | Watch Events (instant, uses a webhook) |
| Delivery updates | Trigger: New Message Status Updated (sent, delivered, read, failed) | Watch Events (you choose which events to watch) |
| Sending | Send Freeform Message, Send Media Message, Send Template Message | Send a Message, Send a Template Message |
| Apps available | 9,000+ (per Zapier) | 3,000+ native apps (per Make) |
| Billing unit | Tasks | Credits |
| Good fit for | Simple, step-by-step flows | Flows with routers, filters, and branches |
Sources: Zapier Help Center, Make Help Center and pricing page. Checked October 15, 2026. Plans and app counts change, so check each site before you buy.
A simple way to choose:
- Want the fastest, simplest setup? Start with Zapier.
- Want branching logic, like “if the message says refund, do X”? Look at Make.
- Want to test for free? Make’s Free plan includes 1,000 credits per month. Make renamed “operations” to “credits.” Existing operations were converted 1:1.
The #1 rule: the 24-hour window, templates, and pricing
This is where most beginners get stuck. Read it twice.
Meta says template messages are the only message type you can send outside a customer service window. When a user messages you, a 24-hour customer service window opens. Messages that are not templates can only be sent inside that open window.
What does that mean for your automation?
Customer wrote to you in the last 24 hours? You can send a normal, free-form reply. Meta charges for these replies after the first 1,000 each month on your business number.
- You want to message first, or 24 hours have passed? You must send an approved template.
Both tools follow this rule. Zapier’s help page says the Send Freeform Message and Send Media Message actions can only be sent within 24 hours of the recipient’s last message. Make’s help page says you can only start new chats with the Send a Template module.
What does it cost?
Since July 1, 2025, Meta charges per message. You are only charged when a message is delivered. Messages that customers send to you are free. Marketing templates are charged, except inside a free entry point window.
Since October 1, 2026, utility templates sent inside an open window are charged too. Free-form replies inside the window are called service messages. The first 1,000 per month on each business number are free. After that, each delivered one is charged. Rates depend on the message category and the recipient’s country calling code.
Meta updated its rate cards on January 1, April 1, July 1, and October 1, 2026. The October 1 update changed 40 rates. It also started charges for service messages and for utility messages sent inside an open window. Always check Meta’s live rate card. Zapier and Make bill you separately for their own usage.
How to connect WhatsApp API with Zapier: step by step
Step 1: Check your account setup
Confirm that you meet the requirements above. You need a paid Zapier plan, Meta Business Manager, a WABA, an approved display name, and opt-in consent from your contacts.
Step 2: Create a new Zap
Click Create and choose Zap. For the trigger app, search for WhatsApp Business.
Step 3: Connect your WhatsApp Business Account
Click Connect WhatsApp Business Account. Log in to your WhatsApp Business Cloud account. Then select your business profile and your WhatsApp business account number. Grant Zapier permission if it asks.
You can also add the connection ahead of time. Go to Zapier’s Apps page, click Add connection, and search for WhatsApp Business.
Step 4: Pick a trigger
Zapier’s WhatsApp Business app has two triggers. New Message Received fires when a message reaches your business number. New Message Status Updated fires when a message you sent changes to sent, delivered, read, or failed.
For a first Zap, pick New Message Received.
Step 5: Test the trigger
Send a WhatsApp message to your business number from your own phone. Then click Test trigger in Zapier. You should see the sender’s details and the message text.
Pro tip: No test data shows up? Check that you sent the message to the business number, not from it.
Step 6: Add your first action
Click + and choose the app where the data should go. For example:
- Google Sheets: create a row
- Your CRM: create or update a contact
- Slack or Gmail: notify your team
Map the fields. Send the sender’s phone number, name, and message text to matching columns.
Step 7: Add a reply action (optional)
Zapier’s WhatsApp Business app has three send actions:
- Send Freeform Message: a text message. Only within 24 hours of the person’s last message.
- Send Media Message: a document, image, video, or audio file. Same 24-hour rule.
- Send Template Message: an approved template. Use this to start a chat or after the window closes.
| Action | Tool | What it sends | When you can use it |
|---|---|---|---|
| Send Freeform Message | Zapier | A text message | Only within 24 hours of the person’s last message |
| Send Media Message | Zapier | A document, image, video, or audio file | Only within 24 hours of the person’s last message |
| Send Template Message | Zapier | A WhatsApp-approved template | Any time. Use it to start a chat or after the window closes. |
| Send a Message | Make | A normal, non-template message | Make’s help page says after you send a template and the customer replies. Meta’s rule is the 24-hour window. Test with a real phone. |
| Send a Template Message | Make | A WhatsApp-approved template | Any time. It is the only way to start new chats. |
Sources: Zapier Help Center, Make Help Center. Checked October 15, 2026.
Since the customer just wrote to you, the window is open. A freeform reply works. Enter phone numbers in international format. Only templates approved by WhatsApp can be used with Send Template Message.
Step 8: Test and publish
Run a full test. Then switch the Zap On.
Important: Zapier says Zap runs always appear as successful, even if the message fails to send. To confirm delivery, review your WhatsApp Business conversations in Meta Business Manager.
Using a Business Solution Provider (BSP)?
Not everyone connects straight to Meta. Many businesses run their number through a Business Solution Provider (BSP). This can change how you connect.
Zapier’s WhatsApp Business app logs in to your WhatsApp Business Cloud account. If a provider manages your number, ask the provider which connection method it supports before you build.
In short: connect the way that matches where your number lives. A mismatch is a common cause of “connection failed” errors.
Still choosing a provider? Wetarseel is a good place to start.
How to connect WhatsApp API with Make: step by step
Step 1: Get your Meta credentials
Make’s help page describes this route. At Meta for Developers, create an app and select Business as the app type. On the app dashboard, find the WhatsApp product and click Set up. Then generate a token.
To connect with Make, you need two values from your WhatsApp Business Cloud account: a permanent token and your WhatsApp Business Account ID. Keep them handy.
Make’s connection screen can change over time. If it shows a guided sign-in instead, follow what you see on screen.
Step 2: Create a scenario
In Make, click Create a new scenario. Add a module and search for WhatsApp Business Cloud. Choose Watch Events.
Step 3: Create the webhook
Watch Events is an instant trigger. Open the module, enter a name for the webhook, and click Save. Then copy the webhook URL. This is the address WhatsApp calls when a message arrives. Add it in the webhook settings of your Meta app.
No polling is needed. The scenario starts as soon as a message lands.
Step 4: Pick the events and test
Select the events you want to watch. For new customer messages, choose messages. Click Run once, then send a test message to your business number.
Step 5: Add a destination module
Click the + beside the trigger. Pick where the data should go. Make lists a ready-made template for this: add a new row to Google Sheets each time a new WhatsApp message arrives.
Step 6: Add a reply module
Make has two message-sending modules:
- Send a Template Message: sends an approved template. Use it to start chats.
- Send a Message: sends a normal, non-template message.
Make’s help page says you can only start new chats with the template module. It adds that you can use Send a Message after you send a template and the customer replies.
Meta’s rule is based on the 24-hour window. So test your flow with a real phone. If Send a Message fails for a customer who just wrote to you, switch to a template.
Step 7: Add filters or a router (optional)
This is where Make shines. For example:
- If the message contains “price,” send it to your sales sheet.
- If it contains “refund,” alert your support channel.
Good news on cost: Make’s help center lists error handler modules as free to use. Make Academy says routers and filters do not count as operations, so they do not use credits.
Step 8: Turn the scenario on
Save it and switch it On. Watch the first few runs in the scenario history. Make shows credit use per scenario, per run, and per module, so you can spot costly steps early. Make says most actions use 1 credit.
3 workflows you can build today
1. Log every new chat as a lead
Trigger: new message received → Action: add a row in Google Sheets or create a CRM contact.
2. Send a template message after a form or order
Trigger: new form entry or webhook → Action: send a template message. Make offers this pattern as a ready-made template: send WhatsApp template messages using a custom webhook. Use a utility template for order updates.
3. Catch failed messages fast
Trigger: message status updated → Filter: status is “failed” → Action: alert your team. In Zapier, use the New Message Status Updated trigger. In Make, check what Watch Events returns for status updates in your setup. Since Zapier runs can look successful even when a send fails, this gives you a second way to catch problems.
Common errors and how to fix them
| Problem | Likely cause | Fix |
|---|---|---|
| I can’t connect my number | A personal number was used, or the display name is not approved | Use a WhatsApp Business Account with a registered number. Get the display name approved in Meta. |
| My message didn’t send | The 24-hour window has closed, or the phone number format is wrong | Send an approved template. Enter the number in international format. |
| My Zap shows success, but the customer got nothing | Zapier says Zap runs always appear successful, even if sending fails | Check your conversations in Meta Business Manager. Add the status trigger as a second check. |
| Make doesn’t fire when I reply from my phone | A Make community member reported that the Watch Events messages trigger fires only on received messages | Check your onboarding path. A separate echo webhook needs a specific onboarding flow. |
| My API key is rejected | A provider key is being used in the wrong app | Some providers’ keys do not work in Zapier’s WhatsApp Business app. Ask your provider which apps it supports. Use the app that matches where your number lives. |
| My Make scenario stopped | You ran out of credits | Add credits. Make queues incoming webhooks, up to your plan’s queue limit, and runs them when scenarios resume. |
Sources: Zapier Help Center, Make help center and community. Checked November 11, 2026.
When Zapier or Make is not enough
Zapier and Make are great for moving data between apps. They are not a full CRM sync.
You may outgrow them if you need:
- Full chat history stored on each contact record
- Two-way sync between WhatsApp and your CRM
- A shared team inbox with assignments
- High message volume, where per-step billing adds up
Don’t guess. Compare your options first. Our complete guide to connecting WhatsApp API with your CRM explains the main approaches, what each one asks of your team, and which one fits which business. It helps you decide before you build the wrong thing.
Best practices for a clean setup
- Start small. Build one workflow. Test it. Then add more.
- Get consent. Only message people who opted in. Zapier lists opt-in consent as a requirement for its WhatsApp Business app.
- Name your templates clearly. You will thank yourself later.
- Check template categories. Meta says businesses are responsible for reviewing the category of each approved template. You accept the charges for that category when you use it.
- Watch your usage. Zapier counts tasks. Make counts credits. Check both dashboards weekly in the first month.
- Test with a real phone. Test data can hide real problems.
- Check Meta’s rate card each quarter. Meta may update pricing only on January 1, April 1, July 1, or October 1.
Final thoughts
Connecting WhatsApp API with Zapier or Make is not hard. The tricky parts are the rules, not the clicks. Get the account setup right. Respect the 24-hour window. Use templates for first contact. Confirm delivery in Meta, not just in your automation tool.
Build one small workflow today. A new chat that lands in a sheet is a great start.
Then ask the bigger question: should WhatsApp sit inside your CRM? Our WhatsApp API and CRM integration guide shows your options, so you can avoid costly rebuilds later.
Frequently Asked Questions (FAQs)
-
Can I use Zapier with a personal WhatsApp number?
No, not with the WhatsApp Business app. It needs a WhatsApp Business Account with a registered business number.
-
Is Zapier's WhatsApp Business app free?
No. Zapier's help page lists it as available on the Professional, Team, and Enterprise plans, and not on the Free plan.
-
Does Make have a free plan?
Yes. Make's Free plan includes 1,000 credits per month. Check Make's app page and pricing page to confirm what your setup needs.
-
Can I send the first message to a customer?
Yes, but only with an approved template. Templates are the only message type allowed outside a customer service window.
-
How long is the free reply window?
A user message opens a 24-hour customer service window. Non-template messages sent inside it are free.
-
Do I pay for WhatsApp messages?
Meta charges only when a template message is delivered. Marketing templates are always charged. Utility templates sent inside an open customer service window are free. Rates depend on the template category and the recipient's country.
-
Why does my Zap show success when the message was not delivered?
Zapier says Zap runs always appear successful, even if the message fails to send. Review your WhatsApp Business conversations in Meta Business Manager to confirm delivery.
-
Do I need to code?
No. Both tools use a visual builder.
-
Which is better for WhatsApp, Zapier or Make?
Neither wins every time. Pick Zapier for speed and simplicity. Pick Make for branching and visual control. Final thoughts