Does Zapier Work With WhatsApp? Every Trigger, Action, and Limit
Zapier connects to WhatsApp through your own WhatsApp Business Account. Here are the two triggers, the three send actions, the 24-hour rule, and why bulk sending breaks.
Yes, Zapier works with WhatsApp. The app is called WhatsApp Business on Zapier, and it connects to your own WhatsApp Business Account through Meta Business Manager. It gives you two triggers, New Message Received and New Message Status Updated, and three send actions: Send Template Message, Send Media Message, and Send Freeform Message. It does not connect to the consumer WhatsApp app or to the free WhatsApp Business phone app, because neither of those has a public API.
That is the short version. The longer version is more useful, because two of those three actions only work for part of the day, and none of them can send to a list.
Two apps with confusingly similar names
Before anything else: Zapier publishes two different things with WhatsApp in the name.
WhatsApp Business is the one that messages your customers. It requires a WhatsApp Business Account with a registered phone number and an approved display name.
WhatsApp Notifications is part of Zapier's own notification tooling and only sends messages to you, the account holder. It is for alerting yourself when a Zap runs, not for talking to customers.
People install the second one, wonder why customers never receive anything, and conclude the integration is broken. It is not. It is doing exactly what it says.
The two triggers
New Message Received fires when a WhatsApp user sends your business a message. This is the trigger most Zaps hang off, and it is doubly important because an inbound message is what opens your 24-hour sending window.
New Message Status Updated fires on a status change: sent, delivered, read, or failed. Route the failures somewhere you will see them. A failed template with its error code attached is a diagnosis; a failed template you never noticed is a customer who never heard from you.
The three actions, and the rule that governs them
WhatsApp will not let a business start a conversation with free-form text. That is Meta's rule, not Zapier's, and every tool on the platform inherits it. When a customer messages you, a 24-hour timer called the customer service window starts. Inside that window you can send more or less anything. Once it closes, you can only send an approved template.
Zapier's actions map onto that rule exactly:
| Action | What it sends | When you can use it |
|---|---|---|
| Send Template Message | One of your pre-approved WhatsApp templates | Any time. Not restricted by the window. |
| Send Freeform Message | Plain text you write in the Zap | Only inside an open 24-hour window |
| Send Media Message | An image, document, or other media file | Only inside an open 24-hour window |
So the shape of a reliable Zap is: something happens, you send a template. Or: a customer writes to you, the window opens, and you reply freeform. Anything that tries to push unsolicited free text at a customer will fail, and it will fail for reasons no amount of Zap debugging will fix.
What you need to connect it
Zapier asks for a Meta Business Manager account, a WhatsApp Business Account with a registered phone number, an approved display name for that WABA, and opt-in consent from the people you intend to message. The connection itself runs through a login flow where you pick the business profile and the number the Zap should send from.
One consequence catches people. Registering a phone number to the WhatsApp Business Platform removes it from the WhatsApp Business app, and the conversation history in that app does not migrate. Use a number you are willing to move permanently.
Can Zapier send bulk WhatsApp messages?
Not in any way you would want to rely on. Zapier's model is one trigger, then a chain of actions, running once per event. There is no action that accepts a list of recipients. To message 4,000 contacts you would need 4,000 Zap runs, and Zapier counts every completed action as a task.
Zapier's free plan includes 100 tasks a month, unlimited Zaps, two-step workflows, and a 15-minute polling interval on polling triggers. Do the arithmetic on a modest campaign and the picture is clear enough without quoting anyone's current paid tier.
The cost is the smaller problem. The real problems are structural:
- No throttling. Firing several thousand templates as fast as the API accepts them is a good way to damage your quality rating and get your messaging tier cut.
- No campaign-level reporting. You get per-Zap task history, not a delivery rate across the send.
- No retry logic. A template that fails on 300 contacts is 300 individual task errors.
- No segmentation. Looping a Zap over spreadsheet rows is not a substitute for an audience.
The sane division of labor is to let Zapier do what it is genuinely excellent at, which is one-to-one automation between apps, and to send the list from a tool built for lists. A form submission fires a Zap that sends a booking confirmation template: perfect. A Tuesday morning campaign to a segment of 5,000: use a WhatsApp bulk sender and trigger it from a Zap if you like. The Zapier WhatsApp integration page lays out which job belongs where.
How to schedule WhatsApp messages in Zapier
There is no native WhatsApp scheduler in Zapier. The two workarounds are a Schedule by Zapier trigger that runs at a set time and then calls Send Template Message, or a Delay step inserted before the send. Both work for a handful of messages. Both consume a task per message, and neither gives you a send window, a throttle, or a report. For a recurring campaign, schedule it where the campaign lives.
What a US business can actually send
This is the constraint that surprises American teams, and again it has nothing to do with Zapier. Since April 1, 2025, Meta has not delivered marketing-category template messages to United States phone numbers. Build a Zap that sends a promotional template to a US customer and it fails with error 131049 through the Cloud API. Meta has given no date for lifting the pause.
Utility templates deliver to US numbers normally: appointment reminders, order and shipping updates, payment confirmations, renewal notices, anything tied to a transaction the customer set in motion. Authentication templates carrying one-time passcodes deliver too. And every freeform reply inside the 24-hour window is both deliverable and free of message charges, which is exactly the case Send Freeform Message exists for.
So the highest-value Zap a US business can build is unglamorous: customer messages you, New Message Received fires, you reply with Send Freeform Message inside the open window, and Meta charges nothing for it. Everything promotional has to reach US customers some other way. Click-to-WhatsApp ads open a free 72-hour window and are the compliant route on WhatsApp itself. For everything else, promotional reach in the US still runs on email, where a personalized outbound sequence does the job WhatsApp marketing templates cannot do here.
Make, n8n, and the direct API
Zapier is not the only automation layer with a WhatsApp Business Cloud connector. Make provides comparable modules and bills by operation rather than by task, which usually works out better once a workflow performs several steps per run. n8n ships a built-in WhatsApp Business Cloud node covering message sends and media upload, download, and delete, and it bills per workflow execution. Its community edition is free if you self-host.
No head-to-head dollar comparison here, because all three vendors revise their tiers and the honest answer depends on how many steps your workflow runs. What does not change is the layer underneath. Each of them still needs a WhatsApp Business Account, still requires an approved template to open a conversation, and still respects the 24-hour window. Changing automation tools does not buy a way around Meta's rules.
If you are comfortable writing a little code, you can skip the automation layer and post straight to the Graph API messages endpoint from your backend. That removes the per-task cost and puts retries and error handling on your terms. Our WhatsApp API integration guide covers the mechanics, and WhatsApp Business API explains how to get access in the first place.
The honest summary
Zapier works with WhatsApp, properly, through the official platform. It is the right tool when one event should produce one message, and when inbound WhatsApp replies need to land in Slack, a CRM, or a task board. It is the wrong tool the moment you need to reach a list, schedule a campaign, throttle a send, or read a delivery rate. Most teams that outgrow it do not abandon Zapier. They keep the Zaps for the one-to-one work and move the list somewhere else.