How to Send a WhatsApp Message Using Zapier (Cloud API Guide 2026)

Searching send WhatsApp message using Zapier usually lands you on a BSP marketing page (WATI’s is the best-known) or on Zapier’s own WhatsApp Notifications app. Those are not the same product. Official business messaging runs on WhatsApp Cloud API: approved templates, a BSP such as Ominiflow, and a Zap that fires when a sheet row, form, or CRM event appears. Unofficial “notifications” Zaps hitch a personal WhatsApp number to WhatsApp Web — they break, they get banned, and they cannot scale.

This is the operator guide we wish ranked instead of a hero banner: how Zapier actually talks to WhatsApp, the two integration types, a no-code setup, a Google Sheets recipe (the Zapier Community thread that still cites WATI), WATI vs Ominiflow, and when you should delete the Zap and use a native connector.

Too long? Start here

• Business path: Trigger app → Ominiflow on Zapier → approved template → customer phone
• Do not use Zapier “WhatsApp Notifications” for customer traffic — it is not Cloud API
• Business-initiated messages need an approved template; free-form text only works inside the 24-hour session
• Phone format: E.164 without plus — India example 919876543210
• Google Sheets new row → template is the most requested Zap; native Sheets on Ominiflow skips Zapier task fees
• WATI’s Zapier page is a landing page. This article is the how-to. Compare stacks: Ominiflow vs WATI
• Zoho / Shopify revenue flows: skip Zapier — native Zoho · Zapier hub. Self-hosted workflows: n8n WhatsApp integration

The Zapier trap: two very different “WhatsApp” apps

Google still ranks Zapier’s WhatsApp Notifications listing for “zapier whatsapp.” That app is a convenience layer around a consumer WhatsApp session. It is not Meta’s Business Platform. If you send order updates or lead follow-ups on it, you are one session logout or quality flag away from silence.

WATI, Interakt, Chatarmin, and Trengo all sell a Zapier connector in front of Cloud API. Ominiflow does the same — plus native Zoho, Shopify, HubSpot, and Sheets so high-volume Zaps do not become a second SaaS bill. Architecture: WhatsApp API integration guide.

How sending a WhatsApp message with Zapier actually works

1. Trigger — Google Sheets new row, Typeform submit, Shopify order, HubSpot deal stage, webhook, schedule
2. Formatter — strip + / spaces from phone; map name, order ID, URL into template variables
3. Action — BSP Zapier action “Send template” or Webhooks by Zapier POST to Cloud API / Ominiflow send endpoint
4. Delivery — Meta sends the template; delivery/read webhooks can write status back (second Zap or native inbox)
5. Reply — customer answers on WhatsApp → BSP shared inbox. Zapier does not replace the inbox

Zapier never “is” WhatsApp. It is glue. The BSP owns the number, templates, quality rating, and conversation history.

Prerequisites

• WhatsApp Cloud API access through a BSP (Ominiflow trial is enough to test)
• At least one approved Utility or Marketing template — name and language code must match character-for-character
• Zapier account (free tier for a POC; paid when you leave task limits)
• Opt-in records for Marketing templates
• Test numbers that actually have WhatsApp installed

Template rules: template message API guide. Session vs template: only after the customer messages you can a Zap send free-form text inside 24 hours.

Step-by-step: send a WhatsApp template from Zapier

1. Connect the BSP in Zapier

In Zapier, open Ominiflow (slug ominiflow) and connect your Ominiflow account. The published action is Send Template Message (send_template_message). Use Webhooks by Zapier only when you need a payload the app does not expose yet — header, button, or more than two body variables.

2. Create the Zap

1. Trigger: pick the source app (start with Google Sheets or Typeform — easiest to debug)
2. Optional Formatter: phone to digits-only, prepend 91 for 10-digit Indian mobiles
3. Action: Send Template Message
4. Required: phone, template_name, template_language (en vs en_US matters)
5. Optional: body_1 and body_2 — only the first two template variables. Templates with more placeholders need Webhooks by Zapier

3. Example Cloud API payload (Webhooks by Zapier)

Use this when you POST from Zapier’s Webhooks “POST” action instead of a branded app:

POST https://graph.facebook.com/v21.0/{PHONE_NUMBER_ID}/messages
Authorization: Bearer {ACCESS_TOKEN}
Content-Type: application/json

{
  "messaging_product": "whatsapp",
  "to": "919876543210",
  "type": "template",
  "template": {
    "name": "lead_welcome",
    "language": { "code": "en" },
    "components": [{
      "type": "body",
      "parameters": [
        { "type": "text", "text": "{{Name}}" },
        { "type": "text", "text": "{{Source}}" }
      ]
    }]
  }
}

In Zapier, replace the quoted {{Name}} values with mapped fields from the trigger step — not WhatsApp template placeholders. Template body Hello {{1}}, thanks for enquiring via {{2}}. needs exactly two parameters, in order. Mismatch returns Graph error #132000.

Store the access token in Zapier’s secret fields. Prefer a permanent system-user token, not a short-lived User token that dies in hours. Developer send patterns: send messages programmatically.

4. Test, then turn on

Send to your own number first. Confirm the green tick, then the reply in the BSP inbox. Only then enable the Zap for production rows. Watch the first 50 Zap runs for skipped steps and 4xx bodies.

Recipe: Google Sheets new row → WhatsApp (the Zap everyone asks for)

Zapier Community threads on “new Google Sheet row to WhatsApp” still point at WATI’s marketing URL. The Zap itself is three steps:

1. Google Sheets — New Spreadsheet Row (or New Row in Worksheet)
2. Filter — phone not empty; optional opted_in column equals yes
3. Ominiflow — Send Template Message — map phone, template_name, template_language, and body_1 / body_2 when the template uses them

Sheet hygiene that saves you a week:

• Header row: phone, name, opted_in, language, custom fields
• Phones as plain text, not Sheets “phone” format that drops the leading country code
• One language per template; do not mix hi and en in the same Zap without a Paths step
• Write-back: a second Zap or native connector stamps sent_at / message_id so retries do not double-send

If Sheets is your CRM, skip Zapier task metering and use Ominiflow’s native connector: Google Sheets + WhatsApp guide.

Other Zaps worth building

Make.com equivalent (more branching, often cheaper per operation): Send WhatsApp from Make. No-code CRM: integrate WhatsApp with CRM without developers.

WATI Zapier vs Ominiflow Zapier vs native

WATI’s /send-whatsapp-message-using-zapier/ page sells “5,000+ apps, no code.” That is true of every BSP Zapier app. The difference is what you still pay Zapier to do after go-live.

Use Zapier where Ominiflow has no native app. Do not put Zapier in the middle of Zoho lead create or Shopify “where is my order?” — those fail at 2am with no thread in the CRM. Deep dive: when Zapier vs native · leave WATI checklist.

Templates, the 24-hour window, and quality rating

• Business-initiated (form, sheet, CRM, schedule) → approved template, correct category
• Customer-initiated (they messaged you) → free-form session messages for 24 hours; a Zap can send text/image if you pass the Cloud API type: text payload
• Marketing templates need documented opt-in. Utility covers confirmations, reminders, shipping
• Blast a cold sheet from Zapier and Meta will drop your quality rating — same physics as any BSP, including WATI
• No URL shorteners in template variables; they look like phishing and fail review

Quality playbook: WhatsApp API quality rating guide.

What it costs

Three meters run at once:

1. Zapier tasks — each successful action step counts. A 3-step Zap × 3,000 rows is 9,000 tasks. Starter plans run out; Professional is the usual production floor
2. Meta conversations (India ballpark): Utility ₹0.115, Marketing ₹0.86 per conversation
3. BSP platform — Ominiflow from ₹15,000/year with Meta at cost; WATI adds contact tiers and often the Zapier bill on top

A 500-message/month pilot is fine on Zapier. A 5,000-order D2C store should move Shopify and Sheets off Zapier. Pricing context: API pricing guide · Ominiflow plans.

Troubleshooting

When to turn Zapier off

• Zoho or HubSpot is the system of record for every lead
• COD confirmation or cart recovery must fire in seconds, not after a Zap queue
• You need the full thread on the CRM timeline, not a one-way send
• Monthly Zapier tasks cost more than the BSP plan
• Ops cannot see failures without opening Zap history

Those jobs belong on native connectors and the visual workflow builder. Zapier stays for the long tail: Calendly, Typeform, Airtable, internal Slack bridges.

Send the first Zap on Cloud API

Ominiflow is on Zapier for the long tail, and ships native Zoho, Shopify, and Sheets so core revenue events do not sit behind a Zap. Use Zapier for glue. Use Ominiflow for the number, inbox, and templates.

Get Zapier + WhatsApp setup help →

Related: Zapier integration · Make guide · API & webhooks · vs WATI

FAQ