How to Send WhatsApp Messages from Make (Integromat): Integration Guide

Make (formerly Integromat) connects 1,000+ apps with visual workflows. Pair it with the WhatsApp Cloud API — Meta's hosted platform, the only supported business path since on-premise was retired in October 2025 — and you trigger messages from Shopify orders, Google Sheets rows, form submissions, or CRM stage changes without writing backend code. This guide covers architecture, step-by-step HTTP setup, template formatting, error handling, and when Make is the right glue vs when native BSP automation wins.

Too long? Start here

• Make scenario = trigger app → data mapping → HTTP POST to Cloud API → template message delivered
• Business-initiated messages need approved templates — free-form text only works inside 24h customer care window
• Phone numbers in E.164 without + : India example 919876543210
• Endpoint: POST graph.facebook.com/v21.0/{PHONE_NUMBER_ID}/messages
• India Meta pricing: utility ₹0.115/conversation, marketing ₹0.86/conversation
• Make excels at cross-app glue; BSP platforms excel at WhatsApp-native inbox, bots, and broadcasts

Why integrate Make with WhatsApp?

Make is middleware — it doesn't replace a BSP inbox, but it bridges systems that don't have native WhatsApp connectors.

Common triggers:

• Shopify order paid → shipping update template
• Facebook Lead Ad → welcome message + assign agent
• Google Sheets new row → interview slot confirmation
• Payment gateway webhook → receipt template
• HubSpot deal stage change → nurture sequence
• Daily schedule → KPI summary to manager's WhatsApp

For core revenue workflows (COD confirm, cart recovery), evaluate native BSP automation first — fewer failure points than a Make chain at scale. See integration guide for the four-pattern framework.

How the integration works

1. Trigger in Make — new row, webhook, schedule, CRM event
2. Data mapping — name, phone (E.164), order ID, template variables
3. HTTP module or BSP connector → WhatsApp Cloud API
4. Template message sent with approved template name + language + components
5. Optional: inbound webhook from BSP inbox for two-way reply routing

Architecture diagram (logical)

Outbound: Shopify webhook → Make scenario → HTTP POST → Meta Cloud API → customer phone

Inbound (if configured): customer reply → Meta webhook → Ominiflow → Make webhook module → Google Sheets / CRM update

Heavy processing after inbound should happen async — Meta expects HTTP 200 within ~5 seconds on webhooks.

Prerequisites checklist

• WhatsApp Cloud API access via BSP (Ominiflow) or direct Meta app
• Phone Number ID and permanent access token
• At least one approved template in utility or marketing category
• Make account (free tier works for POC; paid for production volume)
• Test phone numbers for end-to-end validation

Setup walkthrough: WhatsApp Business API setup

Step-by-step setup

1. Get WhatsApp API credentials

From Ominiflow dashboard or Meta Business Manager:

• PHONE_NUMBER_ID — identifies your sending number
• WABA_ID — WhatsApp Business Account ID
• ACCESS_TOKEN — permanent system user token (store in Make's secure variable, not plaintext)

2. Create approved templates

Utility for order updates; marketing for promos (opt-in required). Note exact template names — Make must match character-for-character. Guide: template message API guide.

3. Build a Make scenario

Example: Shopify → Watch Orders → HTTP POST

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": "order_shipped",
    "language": { "code": "en" },
    "components": [{
      "type": "body",
      "parameters": [
        { "type": "text", "text": "Priya" },
        { "type": "text", "text": "ORD-88421" },
        { "type": "text", "text": "https://track.example/88421" }
      ]
    }]
  }
}

4. Format phone numbers

Strip +, spaces, leading zeros. India: 919876543210. Use Make's replace() and trim() functions on Shopify phone fields — they often arrive as +91 98765 43210.

5. Map template variables

Template Hello {{1}}, order {{2}} shipped. needs exactly 2 parameters in order. Mismatch causes error #132000.

6. Handle errors

Add Make error routes for:

• Template name mismatch (404 / 132001)
• Variable count mismatch (#132000)
• Invalid phone format (#131026)
• Rate limits (#130429) — add retry with backoff

Log failures to Slack or email. Silent Make failures mean customers never get shipping updates.

Popular automation recipes

D2C-specific: Shopify WhatsApp workflows · COD confirmation

The 24-hour rule in Make scenarios

Meta splits messages into two worlds:

• Session messages: Customer messaged you first → 24h window for free-form replies. Make can send text/image via API without template.
• Business-initiated: You reach out first → approved template required.

Most Make scenarios are business-initiated (order triggers, lead forms). Design around templates from day one.

Make vs native Ominiflow automations

Best practice: Ominiflow for customer conversations and WhatsApp-native flows; Make for back-office glue (Sheets, Slack, niche SaaS).

Zoho teams: skip Make entirely — native Zoho integration.

Cost model

Make operations + Meta conversation fees + BSP platform (if using Ominiflow for credentials and inbox).

India Meta ballpark: utility ₹0.115/conversation, marketing ₹0.86/conversation. A scenario firing 3,000 order updates/month = ~₹345 Meta utility fees. Make Core plan (~$9/month) covers moderate volume; watch operation counts on high-frequency triggers.

Troubleshooting

Start with Ominiflow + Make

Ominiflow provisions Cloud API access, approves templates, and wires webhooks so Make scenarios stay reliable in production. Use Make for cross-app triggers; use Ominiflow for inbox, bots, and broadcasts.

Request Integration Help →

Related: automation platform · Zapier + WhatsApp · API & webhooks

FAQ