WhatsApp Automation with Make: A Practical Guide

You automate WhatsApp with Make by adding its official WhatsApp Business Cloud app to a scenario, connecting it with your Meta Cloud API credentials, and then using modules to send template messages and catch incoming replies as steps in a visual flow. Make is best for event-driven messages, where something happening in another app triggers a WhatsApp message: a new order sends a shipping update, a form submission sends a confirmation, a calendar event sends a reminder. It is not a bulk campaign tool, and knowing that line saves you a lot of frustration.

This guide walks through how the integration actually works, three scenarios worth building, and the point where you should reach for a dedicated sender instead.

How the WhatsApp app in Make works

Make, which was called Integromat until 2022, is a no-code automation platform built around scenarios: a trigger in one app fires a chain of actions in others. The WhatsApp Business Cloud app is Make's official connector to Meta's Cloud API, and Make builds and maintains it. You connect it once with your access token, phone number ID, and WhatsApp Business Account, and then WhatsApp becomes a step you can drop into any flow.

The modules split into triggers and actions. Watch Events is the trigger: it fires when a new message comes in or a message status changes to sent, delivered, or read. On the action side, Send a Template Message sends an approved template and is the only way to start a conversation with someone who has not messaged you. Send a Message sends free-form text, but only inside the 24-hour window after the customer wrote to you. Send a Media Message attaches an image or document, and Make an API Call handles anything the prebuilt modules do not. The Make WhatsApp integration page has the full module list and setup steps.

The 24-hour window is built into the modules

The single rule that shapes every WhatsApp automation is the 24-hour customer service window. To message someone who has not contacted you, or whose last message was more than 24 hours ago, you must use Send a Template Message with an approved template. Only after they reply can you use Send a Message for free-form text, and only for the next day. This is Meta's rule, enforced the same way in every tool built on the WhatsApp Cloud API. Make just surfaces it as two different modules, which is a helpful reminder of which one you are allowed to use.

Three scenarios worth building

The first is order updates. Trigger the scenario from a new paid or shipped order in your store or a new row in a sheet, then fire a utility template with the order number and status. Because it is a utility template, it delivers to US numbers too. The second is appointment reminders. Trigger from a calendar or booking tool a day ahead, and send a reminder template. The third is lead handling. When a form or ad lead lands, message the lead with a template and, in the same scenario, alert the right salesperson in Slack or your CRM. Add a Watch Events branch to log any reply back to the CRM.

A common fourth pattern is turning documents into messages. If your scenario needs the contents of an uploaded receipt or invoice, you can add a step that runs the file through AI receipt and invoice data extraction to get clean, structured fields, then feed those values into your template variables. That keeps the whole flow no-code, from a photographed receipt to a WhatsApp confirmation.

Where Make stops and a bulk sender starts

Make is superb at one-at-a-time, triggered messages. It is awkward at campaigns. It has no concept of an audience, no template editor, and no campaign analytics. You can loop over rows in a sheet to message a list, but it is clumsy, it gives you no delivery reporting, and you are hand-rolling something that dedicated tools do natively.

So the clean division of labor is this: use Make for automations that react to events in your other tools, and use a WhatsApp bulk sender when you need to send one approved template to a whole audience and see who received, read, and replied to it. They run on the same Meta Cloud API and the same number, so most teams use both. Reach for Make when the message is a reaction to something. Reach for a bulk sender when the message is a campaign.

Getting started

You need a WhatsApp Business Account on Meta's Cloud API before anything works in Make, so set that up first and grab your access token and phone number ID. Then add the WhatsApp Business Cloud app to a scenario, create the connection, pick a trigger, and add Send a Template Message. Test with a template you have already had approved. Once the first scenario runs cleanly, the rest is just wiring more triggers to the same send step. Start with order updates, since utility templates deliver everywhere and the value is immediate.