You can connect WhatsApp to Make with two modules that come with every Make plan: one receives the messages customers send you, and one sends your replies. There is nothing to install and no server to run. Once connected, your scenarios send order updates, reminders, and follow-ups from your own business number the moment something happens in the tools you already use. This guide walks through the setup, the Make plan limits to prepare for, and how to test before a customer sees a message. To compare this with six other supported tools, read our WhatsApp automation overview.
Key Takeaways
- You need three things: a WhatsApp number on the official API, a Make account, and about 30 minutes.
- Make’s Free plan is enough for testing, but a live two-way setup usually needs a paid plan because every step in a scenario uses credits.
- You can test the whole setup on your own phone first, so no customer ever sees a test message.
- Automated messages and your team’s manual replies can share the same WhatsApp number.
- More than 24 hours after a customer’s last message, WhatsApp only delivers templates, which are message formats Meta approves in advance, so plan reminders and order updates as templates.
What Does a Make WhatsApp Integration Give You?
A Make WhatsApp integration lets your scenarios send and receive WhatsApp messages from your own business number, with no server to run and no code to deploy. Customers see your verified business name, and every message travels through the official WhatsApp Business API, the version Meta provides for businesses.
When a customer messages you, the scenario starts instantly, so the same flow can read what they wrote and reply. A 360Dialog number and a Make account are all you need to start sending.
If your business does not have a WhatsApp number on the official API yet, get API access first, then follow the three steps below to connect it to Make.
When Should You Connect WhatsApp to Make?
Make is a good fit when your team already uses it and you want WhatsApp messages to go out automatically when something happens:
- You already build scenarios in Make. If you have used the Webhooks and HTTP modules before, the setup will be quick. If Make is new to you, build one simple scenario first to learn the interface.
- You expect steady message volume. Make’s Free plan includes 1,000 credits per month, up to 2 active scenarios, and at least 15 minutes between scheduled runs.[1] Each step in a scenario uses a credit, so one customer message that triggers a lookup and a reply can use several. Paid plans remove the scenario limit, and Make shows their prices for your region on its pricing page.
- You want events handled automatically. Order updates, follow-ups, appointment reminders, and CRM updates work well. Conversations that need a person belong in a shared inbox, covered further down.
If your team already works in Zapier or runs a self-hosted workflow tool, the same 360Dialog API connects to both. See the WhatsApp Zapier integration guide or the n8n WhatsApp integration walkthrough, or compare all on our WhatsApp integrations page.
How Does Automation Differ From Live Chat?
Automation sends the right message when something happens, and live chat is a person answering customers in real time. Make watches Shopify, Typeform, Google Sheets, or any of the 3,000+ apps in its library, and sends the matching WhatsApp message on its own. When a customer replies with a question the scenario cannot answer, a person needs to pick it up. Both can run on the same number, as step 2 explains.
Connect Your Account in 3 Steps
Connecting takes three things: a key from the 360Dialog Hub, a web address for incoming messages, and one module that sends messages out:
Step 1: Store Your API Key in a Make Keychain
Your API key is the password that lets Make send messages from your number. Open the 360Dialog Hub, select your WhatsApp number, and copy the key from API Settings. In Make, add an HTTP > Make a request module, set the authentication type to API key, and create a keychain. Paste the key exactly as copied with nothing added in front of it, set the placement to the header, and enter D360-API-KEY as the parameter name.[2] Make recommends keychains because the key stays hidden inside the module, and replacing the key later updates every module that uses it.
Step 2: Set Up the Webhook (Inbound)
A webhook is the web address where WhatsApp delivers the messages customers send you. Add a Webhooks > Custom webhook module to your scenario and copy the address Make creates. Paste it into the 360Dialog Hub under your number’s webhook settings, then enter the verification code 360Dialog emails you. The webhook goes live once you confirm the code.[3]
360Dialog requires each delivery to be confirmed within 5 seconds and rejects addresses with underscores or port numbers in the domain.[4] Make’s webhook addresses meet both rules. Make confirms each message as soon as it arrives and holds it in a queue until the scenario runs.[5] Make also switches off a webhook that stays unattached to any scenario for more than 5 days, so connect it to a scenario soon after creating it.
Each number delivers incoming messages to one webhook by default, so pointing your number at Make stops delivery to any tool that received those messages before. To keep several tools receiving from the same number, turn on multi-webhook, which delivers every incoming message to more than one address. It takes one API call: a POST request to the /multi_webhook endpoint using the same key.[6]
Step 3: Configure the HTTP Module (Outbound)
The HTTP module is what sends your WhatsApp messages. In the module from step 1, set the method to POST, the URL to https://waba-v2.360dialog.io/messages, and the body type to JSON. The body needs four fields: messaging_product, recipient_type, to, and type.[7] Write the recipient’s number as country code plus digits, with no plus sign and no spaces.
A response that contains an id means Meta accepted the message, and delivery and read updates arrive later through your webhook. To handle failures, attach an error handler route to the HTTP module. Error handlers such as Resume, Rollback, Commit, Break, and Ignore use no credits.
Test in the Sandbox First
The 360Dialog sandbox lets you run the whole scenario on your own phone before a customer sees anything.[8] Send START to the sandbox number on WhatsApp to receive a test key. Then register your Make webhook with a POST request to https://waba-sandbox.360dialog.io/v1/configs/webhook, point the HTTP module at https://waba-sandbox.360dialog.io/v1/messages, and save the test key in its own keychain. The sandbox accepts up to 200 requests, all to your own number, so switch to your live number and key once everything works.
After you go live, WhatsApp’s 24-hour rule applies. Each time a customer messages you, a 24-hour window opens in which you can send any kind of message. Outside that window, WhatsApp accepts only approved templates.[9]
What Do People Automate With Make and WhatsApp?
Lead follow-up, CRM sync, order updates, and appointment reminders are the four most common scenarios, and each one uses the same webhook and HTTP setup:
- Lead follow-up. A Typeform submission starts the scenario, and the lead receives a WhatsApp message while still on the page.
- CRM sync. Every message a customer sends is saved to HubSpot or a Google Sheet with the sender, the text, and the time, so nobody has to copy it over by hand.
- Order updates. Shopify marks an order as shipped, Make sends an approved template with the tracking link, and customers stop asking where their package is.
- Appointment reminders. A Google Calendar event or Airtable row starts the scenario, and the customer receives an approved template at the scheduled time.
Does Your Team Need a Shared View?
Your team needs a shared view once customers reply to automated messages with questions a person has to answer. Our WhatsApp team inbox puts several agents on the same number your scenarios use, with assignment, tags, and saved replies. With multi-webhook turned on, the inbox and your Make scenario both receive every incoming message, so an automated order update and a human follow-up stay in one conversation.
Talk to us about running our WhatsApp team Inbox product and Make together.
Why 360Dialog?
360Dialog is an Official Meta Solution Partner providing WhatsApp Business API infrastructure to 100,000+ businesses sending 2 billion messages. Connecting Make through 360Dialog gives you number management in the 360Dialog Hub, 24/7 support in seven languages, and Meta’s messaging fees with no markup, on plans from €49 per number per month.
Make’s own WhatsApp Business Cloud app is another option, and it connects your number straight to Meta.[10] With that app, you register the number and set up its two-step verification yourself through the app’s modules, without the 360Dialog Hub or our support team behind it.
Your number, your API key, and your Make scenarios are everything this setup needs. Once your sandbox test passes, get API access on a plan that fits your volume and point your first live webhook at Make.
Note: Make’s library also lists apps with similar names from unrelated companies. 360Messenger for WhatsApp, for example, is published by 360messenger, which has no connection to 360Dialog.[11] Its own FAQ says it connects numbers running the regular WhatsApp or WhatsApp Business app, so just keep in mind that its keys will not work with a 360Dialog number.[12] Check who publishes a WhatsApp app before you connect it.
Frequently Asked Questions
How Do I Connect WhatsApp to Make?
Use two modules that come with Make. The Custom webhook module from Make’s Webhooks app receives customer messages, and you register its address in the 360Dialog Hub and confirm it with a code sent by email. The Make a request module from the HTTP app sends your messages through 360Dialog, with your API key stored in a keychain under the header name D360-API-KEY. Turn the scenario on, and messages flow both ways.
Is the Make WhatsApp Integration Official?
The API is official. Your number runs on the official WhatsApp Business API through 360Dialog, an Official Meta Solution Partner. The scenario is built from Make’s standard Webhooks and HTTP modules, which you own and can change at any time, and no unofficial workaround sits in between.
Can I Test the Integration Before Going Live?
Yes. The 360Dialog sandbox has its own API key and accepts up to 200 requests addressed to your own phone number. Point the HTTP module at the sandbox messages endpoint, run the scenario, then swap in your live key and the live endpoint.
Do I Need a Developer to Set This Up?
Most Make users can set this up without a developer. There is no server to run and no code to deploy. You fill in a short JSON body in the HTTP module and paste one address into the 360Dialog Hub. If you have used the HTTP module before, every step will look familiar, and the setup takes about 30 minutes.
Can I Still Reply Manually While a Scenario Is Running?
Yes. By default, all incoming messages for a number go to one webhook, so if Make holds that webhook, incoming messages go to Make. Turn on multi-webhook for the number, and a shared inbox receives the same messages alongside your scenario, so your team can reply by hand without interrupting the automation.
Sources
[1] Make, “Pricing,” make.com, accessed September 25, 2026. https://www.make.com/en/pricing
[2] Make, “HTTP” and “API Key Authentication Type,” apps.make.com, accessed September 25, 2026. https://apps.make.com/http and https://apps.make.com/api-key-authentication-type
[3] 360Dialog, “Webhook URL,” docs.360dialog.com, accessed September 25, 2026. https://docs.360dialog.com/docs/hub/webhook-url
[4] 360Dialog, “Webhooks,” docs.360dialog.com, accessed September 25, 2026. https://docs.360dialog.com/docs/messaging/webhook
[5] Make, “Webhooks,” help.make.com, accessed September 25, 2026. https://help.make.com/webhooks
[6] 360Dialog, “Webhooks API Reference,” docs.360dialog.com, accessed September 25, 2026. https://docs.360dialog.com/docs/messaging-api/api-reference/webhooks
[7] 360Dialog, “Send and Receive Messages,” docs.360dialog.com, accessed September 25, 2026. https://docs.360dialog.com/docs/guides/send-and-receive-messages
[8] 360Dialog, “Sandbox,” docs.360dialog.com, accessed September 25, 2026. https://docs.360dialog.com/docs/get-started/sandbox
[9] Meta, “Pricing on the WhatsApp Business Platform,” developers.facebook.com, accessed September 25, 2026. https://developers.facebook.com/docs/whatsapp/pricing
[10] Make, “WhatsApp Business Cloud Integration,” make.com, accessed September 25, 2026. https://www.make.com/en/integrations/whatsapp-business-cloud
[11] Make, “360Messenger for WhatsApp Integration,” make.com, accessed September 25, 2026. https://www.make.com/en/integrations/whatsapp-360messenger
[12] 360messenger, “FAQ,” 360messenger.com, accessed September 25, 2026. https://360messenger.com/en/
