Builder · Level 2 of 3
Make’s WhatsApp Business Cloud app connects a business number to Meta’s messaging platform so workflows can receive events and prepare permitted replies or templates. You need the appropriate Meta business accounts, number, connection and messaging permissions. Start with a controlled test recipient, an approved template where required, and a record of what happened. The scenarios below are desk-researched designs, not AML-tested live messaging workflows.
Some links below are affiliate links. If you sign up through them, Automate My Life may earn a commission at no extra cost to you, which helps keep the site free. Only genuinely useful tools receive a recommendation.
What Make’s WhatsApp Business Integration Actually Does
Make’s WhatsApp Business Cloud app lets a scenario watch for events (new messages, status updates), send plain messages, send pre-approved template messages, upload and download media, and read or update your business profile. It is not a chatbot builder and it is not the WhatsApp Business mobile app. It is a connector to Meta’s Cloud API, which means the setup work happens on Meta’s side first and Make only shows up at the end.
Before you open Make, you need:
- A Facebook account and a Meta Business Suite account, with a business portfolio created inside it.
- A WhatsApp Business account (WABA) attached to that portfolio, plus a valid WhatsApp Business number. If you already run the free WhatsApp Business phone app on that number, Meta’s “coexistence” connection mode lets the Cloud API and the phone app share it, though coexistence is not available in every country.
- Follow the current connection instructions for your exact number and signup mode. Make’s requirements mention disabling two-step verification during setup; treat that as a specific setup step, keep the PIN secure, and follow the supported verification process afterward rather than leaving account security unchecked.
With those in place, add a WhatsApp Business Cloud module to a Make scenario and click Add next to the connection field. Choose Regular signup mode unless you specifically need coexistence, pick your business portfolio, and either select an existing WABA or create one on the spot. Meta then reviews your business name and display name, which usually takes about a business day. While that review is pending, you can still send up to five business-initiated test messages every 24 hours, enough to confirm the connection works before you build anything real.
If you have never built a Make scenario at all, it is worth starting with Make.com for Beginners: How to Build Your First Scenario first, then coming back here once the interface itself feels familiar.
Design an Order-Confirmation Scenario
The clearest way to see how this fits together is a single, common workflow: a customer places an order somewhere else in your stack, and Make sends them a WhatsApp confirmation automatically. This example uses Shopify as the order source, but the same pattern works with any app that has a “new order” or “new record” trigger.
- Trigger: Shopify > Watch Orders. Select the intended order event and require a valid phone number plus recorded permission for WhatsApp contact. A phone number on an order is not, by itself, opt-in consent. Exclude opted-out recipients before the send step.
- Validate the recipient. Use a country-aware phone-number validator and the format required by the connector. Do not strip leading zeroes indiscriminately or guess a missing country code. Keep invalid or ambiguous numbers in a review queue instead of messaging a guessed recipient.
- Action: WhatsApp Business Cloud > Send a Template Message. Use your approved order-confirmation template and map only validated order fields. An order event does not prove an open WhatsApp service window. Check opt-in, template status and recipient again before this action; do not guess a delivery date that your order system has not provided.
- Reserve and record the send. Use a stable order/event ID to prevent the same confirmation from being created twice. Save the provider message ID and later delivery status, with only the customer data needed for support. A successful module response is not proof that the customer received or read the message. Reconcile an uncertain result before another create attempt.
That covers a business-initiated message. The other half of a useful setup is replying to messages customers send you, which uses a different module. Add a second, separate scenario:
- Trigger: WhatsApp Business Cloud > Watch Events (instant). This is a webhook-based module, so it fires the moment a message arrives instead of polling on a schedule. Set up the webhook once against your connection and select the message events you want to watch.
- Route the request. Keywords can identify an order-status question, but they do not authenticate the customer. Verify access to the requested order before returning private details, and send ambiguous questions to a human support path.
- Action: WhatsApp Business Cloud > Send a Message. Because this reply happens inside the 24-hour window the customer’s own message just opened, it can be a plain text message, no template or pre-approval needed. Pull the order status from Shopify (or your order system) and drop it straight into the reply text.
Two scenarios, two modules, and the distinction between them (Send a Template Message versus Send a Message) is the whole ballgame for understanding what you can and cannot automate here.
The 24-Hour Service Window and Template Approval, Explained
A customer message opens or resets the 24-hour customer-service window described in Meta’s messaging policy. Within it, permitted replies can use a non-template message. Outside it, use an approved template for the appropriate purpose. Do not infer a window from a Shopify event or an unrelated contact with the customer.
Prepare templates in WhatsApp Manager and check their current approval and category before enabling a workflow. An order confirmation should contain the transaction information the customer expects, rather than mixing in a promotion. Leave review time in your launch plan; approval is an account outcome to check, not a promised number of hours.
The order-confirmation design uses an approved transaction template because an order event alone does not establish an open service window. The incoming-message design can use a permitted plain reply while the customer’s message window is still open. Check the current state at send time; a queued reply may outlive the window that existed when it was prepared.
What Breaks: Rate Limits, Template Rejections, and the Real Per-Message Cost
Three things catch people off guard once a WhatsApp automation is actually running.
- Template rejections and recategorization. A utility template that reads as promotional, or that leaves a variable slot with no surrounding context (a template that is only “{{1}}”), does not get quietly approved as-is: Meta either rejects it outright or reclassifies it as marketing, which carries different rules and cost than the utility category you intended. Editing a template’s content or category sends it back through review, so treat your first submission as the one that needs to be right rather than something you will iterate on live.
- Messaging limits. Read the current limit and quality status in WhatsApp Manager for your business portfolio. Verification, history and message quality affect capacity. Do not design around an assumed universal starting allowance or treat a higher limit as permission to contact people who did not opt in.
- Meta pricing and allowances. Confirm the current delivered-message charges, categories, markets and any free allowance in your own billing view and rate card. No account-specific billing quote was verified for this guide, so it does not promise that every reply is free or that every reply is charged. Resolve the applicable rates and allowances before enabling volume.
Budget Meta messaging charges separately from Make credits and any Shopify or helpdesk plan. One order can trigger several Make operations: polling, validation, lookups, a send, logging and error handling. Count bundles and retries as well as the happy path. The workflow is not one scenario execution equals one credit or one guaranteed delivered message.
Make vs. the Raw WhatsApp Cloud API vs. a Dedicated WhatsApp Tool
Make is not the only way to automate WhatsApp Business, and it is not always the right one.
| Option | Setup effort | Ongoing cost | Best for |
|---|---|---|---|
| Make.com (this guide) | Moderate: Meta business verification, then drag-and-drop scenario building | Make credits plus applicable Meta charges | Wiring WhatsApp into an existing stack (Shopify, Sheets, a CRM) without writing code |
| Raw WhatsApp Cloud API | High: direct API calls, your own webhook server, your own retry and error handling | Meta charges plus your hosting, engineering and maintenance costs | Teams with developer time who need full control or very high message volume |
| Dedicated WhatsApp tool (e.g. a WhatsApp-specific chatbot or helpdesk platform) | Low: guided onboarding built specifically for WhatsApp | Flat monthly subscription, sometimes bundled with per-message costs | Teams that want a WhatsApp inbox and basic automation but nothing else in their stack connected |
Reach for Make when the WhatsApp piece is one node in a larger automation, your order confirmation, your CRM update, and your WhatsApp message all need to fire from the same trigger. Reach for the raw Cloud API when you have engineering time and need behavior Make’s modules do not expose, or when message volume is high enough that Make’s per-operation billing adds up faster than a direct integration would. Reach for a dedicated WhatsApp tool when WhatsApp is the entire job (a support inbox, a broadcast list) and you have no real need to touch the rest of your stack. If you are still deciding whether Make, Zapier, or n8n is the right general-purpose platform for your automations before you even get to WhatsApp specifically, Zapier vs Make vs n8n in 2026: The Honest Comparison lays out the tradeoffs.
Setup Cost and Ongoing Maintenance
Allow for connection setup, business review, template approval and controlled tests before setting a launch date. The elapsed time depends on your account and workflow. No setup duration or successful live send was measured for this guide.
Make advertises a Free allowance of 1,000 credits, but check the modules, scheduling interval and current paid quote you need. Count the entire scenario and any Meta charges separately. You can check Make’s current options before buying a plan; a free Make account does not establish that Meta messaging is free.
Review failed or paused templates, connection health, quality status, opted-out contacts, credits and provider delivery receipts. Keep a direct route to human support, as Meta’s policy requires for automated replies. Pause the sending path when authentication, consent or delivery state is uncertain, rather than letting retries create duplicate customer messages.
Evidence and Verification
Desk review, October 30, 2026: Make’s app documentation supports the connector and connection flow; Meta’s messaging policy supports opt-in, templates, the service window and human escalation. Check Meta’s current pricing and your account’s rate card for a usable billing quote. No AML live connection, message send, delivery test or usage benchmark was performed. These scenarios require account-level validation before production.
Before enabling the schedule, test one controlled recipient, an opted-out record, a malformed number, a duplicate order event, an expired service window, a rejected template and an ambiguous timeout. Verify that each error stops or routes to review as intended. Keep customer sends disabled while checking these cases; the checklist describes required validation, not tests AML performed.