How to Connect WhatsApp to Make.com (No Code Required)

Most teams that use Make already have a dozen scenarios running in the background: leads go into the CRM, invoices get filed, Slack gets pinged when something breaks. Yet when it is time to actually tell a customer something, the scenario usually ends with an email. This guide shows you how to send WhatsApp messages from Make in about ten minutes — no code, no developer and no Meta Business API approval.

Why Make Works So Well for WhatsApp

Make (you might still know it as Integromat) is built for scenarios that branch. One trigger can split into different paths depending on the data, and each path can do something different. That suits WhatsApp well, because the right message usually depends on who the customer is and what just happened:

• A new order comes in. Cash-on-delivery customers get a confirmation request; prepaid customers get a thank-you.
• A form is submitted. High-value leads go straight to a sales rep's WhatsApp; everyone else gets an automatic reply.
• A support ticket changes status, and the customer hears about it right away instead of refreshing an inbox.

Make does have its own WhatsApp Business Cloud module, but it needs a Meta developer app, a verified business and an approved number before you can send anything. SyncMate skips all of that by connecting your existing WhatsApp or WhatsApp Business account in one QR scan. To compare costs, see our guide to WhatsApp Business API pricing in 2026.

What You'll Need

• A Make account. The free plan is fine for testing.
• A SyncMate account. The free plan includes 450 WhatsApp messages a month.
• Your phone with WhatsApp on it, so you can scan a QR code.
• Something to trigger the scenario, such as a Google Sheet, a Shopify store, a HubSpot account or a webhook.

How to Set Up the Make.com WhatsApp Integration

Step 1: Create a scenario and choose a trigger

Log in to Make, click Create a new scenario, then click the + to add your first module. This trigger decides when a WhatsApp message goes out. Common choices:

• Google Sheets → Watch Rows for lists, bookings and form responses
• Shopify → New Order for order updates
• HubSpot → New Contact for lead follow-ups
• Webhooks → Custom Webhook for anything that can send an HTTP request

Connect the trigger app as usual and, if you can, run it once so Make has sample data to map in the next steps.

Step 2: Add the SyncMate WhatsApp module

Click the + after your trigger and search for WhatsApp Notifications and Alerts by SyncMate. You will see three actions:

• Send Message to Number — for individual customers or teammates
• Send Message to Group — for team or community groups
• Send Message to Channel/Newsletter — for broadcast-style updates

Pick Send Message to Number for your first test.

Step 3: Connect your SyncMate account and WhatsApp

Click Add Connection and log in to your SyncMate account when prompted. Click Generate QR Code, then on your phone open WhatsApp, go to Linked devices and scan the code. Once it shows as connected, authorise the connection. You only do this once — every future scenario can reuse it. Stuck? Follow Connect your Make with SyncMate.

Step 4: Write your message and map the data

In the phone number field, map the number from your trigger and make sure it includes the country code (for example, +919876543210). In the message field, write your text and insert fields from earlier modules. A booking reminder built from a Google Sheet might read:

Hi {{name}}, just a reminder about your appointment on {{date}} at {{time}}. Reply here if you need to reschedule.

Each {{field}} is a value mapped from your sheet, so every person gets their own details.

Step 5: Test with Run Once

Click Run once, then trigger the scenario — for example by adding a test row to your sheet. The message should arrive within a few seconds. Make shows a bubble on each module with what went in and what came out, which is the fastest way to spot a mapping mistake.

If nothing arrives, open the Logs section in your SyncMate dashboard: it shows whether each message was sent, delivered or failed. The message not received guide covers the usual causes.

Step 6: Switch the scenario on

Once the test works, toggle the scenario On and choose how often it should check for new data. Your WhatsApp automation in Make is live.

Sending to WhatsApp Groups and Channels

Switch the action to Send Message to Group and enter a Group ID instead of a phone number. WhatsApp does not show group IDs in the app, so use our free WhatsApp Group ID finder. For channels, choose Send Message to Channel/Newsletter and paste the channel ID — the WhatsApp Channel ID finder shows you how to get it.

Groups work well for internal alerts, like a daily sales summary for your team. Channels are better for one-to-many announcements, such as new products or offers.

5 WhatsApp Automation Ideas for Make

1. Order confirmations and COD checks. Shopify → New Order, then a Router that sends different messages for prepaid and cash-on-delivery orders. Prefer not to build it? The Shopify WhatsApp integration handles this out of the box.
2. Lead follow-up in under a minute. HubSpot → New Contact, then an instant WhatsApp to the lead and a heads-up to the assigned rep. The HubSpot WhatsApp integration can also log those chats back to the contact.
3. Appointment reminders. A scheduled scenario reads tomorrow's bookings from Google Sheets or Google Calendar and messages each person the evening before.
4. Payment nudges. When an invoice passes its due date, send a polite reminder with the payment link.
5. Team alerts. Low stock, a failed payment or a five-star review can each trigger a message to the right WhatsApp group.

Tips to Keep Your Scenarios Running Smoothly

• Add a Filter before the WhatsApp module. Only send when the phone field is not empty and the number looks valid — it saves operations and avoids failed sends.
• Clean phone numbers early. Use Make's text functions to strip spaces and dashes, and add the country code if your source leaves it out.
• Pace bulk sends. If a scenario might send hundreds of messages at once, add a Sleep module or spread runs across the day. Our account safety guide explains why.
• Keep WhatsApp connected. If your linked session is logged out, messages wait in the queue. Here is how to check whether WhatsApp is connected.
• Watch limits on both sides. Make counts operations and SyncMate counts messages; a busy scenario uses both.

Make, Zapier or n8n: Which Is Right for WhatsApp?

SyncMate works with all three, so the right choice comes down to how you like to build:

• Make suits scenarios with branches, filters and routers, all laid out visually.
• Zapier is the quickest for simple trigger-to-message flows. See the Zapier WhatsApp integration.
• n8n fits technical teams who want to self-host. Our guide on sending WhatsApp messages from n8n covers that setup.

Final Thoughts

A Make.com WhatsApp integration takes one module and one QR scan. The real work is choosing the moments worth a message. Start with a single scenario — order confirmations or appointment reminders are good first picks — watch the logs for a week, and branch out once you trust it. See everything SyncMate can do inside Make on the Make WhatsApp integration page.

Frequently Asked Questions