Put WhatsApp
in any Zap.
A customer messages your WhatsApp number and your Zap runs the same second - into a sheet, a channel, a CRM, whatever you already use. And any Zap can send an approved WhatsApp template back out.
Four things start a Zap.
Each one arrives with its own fields, flat and already named, so you can map them straight into the next step without unwrapping anything.
New WhatsApp Message
Fires the moment a customer sends your WhatsApp Business number a message.
- from
- contact_name
- text
- type
- wamid
Message Delivery Status Changed
Fires when a message you sent moves to sent, delivered, read or failed. Only forward moves fire, so one message never reports the same status twice.
- status
- previous_status
- to
- wamid
Template Approved by Meta
Fires when Meta approves one of your templates, which is the moment you can start sending it.
- template_name
- language
- category
Connection Health Issue
Fires when a number is frozen, or when Meta drops its quality rating to YELLOW or RED.
- kind
- phone_number
- quality_rating
And three things a Zap can do back.
A Zap started by anything at all - a new row, a paid invoice, a form - can finish by messaging the customer on WhatsApp.
Send WhatsApp Template
Send an approved template to a number. The only kind of message allowed outside the 24-hour window after the customer last wrote to you.
Send WhatsApp Text Reply
Send a plain text message. WhatsApp allows this only within 24 hours of the customer's last message.
Create Broadcast Campaign
Queue a template campaign to a list of numbers. Created as a draft unless you switch on “Send immediately”.
The number and the template are dropdowns in Zapier, filled from your own account, so there are no ids to look up by hand.
Three steps, done once.
- 1
Connect the card
Open Integrations in your dashboard and switch Zapier on. That is the whole connection step - there is nothing to install.
Connected - 2
Make an API key
Create a key with the three scopes Zapier needs. It asks for the key once, when you add the account.
messages:sendmessages:readsubscriptions:write - 3
Build the Zap
Pick an AiOneChat trigger, pick what happens next, turn it on. Zapier registers the hook for you the moment you do.
Zap is on
Built so it cannot run twice.
The connector uses REST hooks, and the rules around them are the part that decides whether an automation can be trusted with a customer’s phone number.
Instant, not polling
Zapier subscribes a hook URL and we post to it the moment the event happens. Nothing waits for a poll interval.
One event, one Zap run
Every delivery carries its own id at the top level, which is the field Zapier dedupes on. A retry cannot run your Zap twice.
Deleting the Zap is enough
A deleted Zap answers 410 Gone. We take that as the subscription being over and stop posting to it - no cleanup on your side.
A dead URL switches itself off
Ten deliveries in a row that fail disable that subscription, with the reason recorded, rather than retrying forever.
https only, public addresses only
A hook URL must be https. Localhost, private ranges and link-local addresses are refused, so the connector can never be pointed back into our own network.
Scoped API keys
The key you paste into Zapier carries only the scopes you ticked. A key without subscriptions:write cannot create a hook at all.
When a Zap doesn’t fire, the page says why.
Most connectors leave you guessing between your tool and theirs. Your Zapier card keeps its own count, a bar per day, and one row per delivery - each with the reason attached.
syncedthe Zap took itfailedthe Zap answered HTTP 500, or could not be reachedskippedthe Zap answered 410 Gone and was switched off
- numbers masked
- kept 30 days
- refresh in place
template/approvedskippedthe Zap answered 410 Gone, so its subscription was switched off—message/inboundfailedthe Zap answered HTTP 500•••• 3344message/statussynced•••• 2233message/inboundsynced•••• 3210Numbers are shown masked. Events are kept for 30 days, then expire on their own.
Wire WhatsApp into what you already use.
Switch the Zapier card on, create a scoped API key, and build your first Zap.