How to Send WhatsApp Notification from Make.com or n8n

If you need to send WhatsApp messages from an automation, the fastest reliable route is to use the WhatsApp Business Cloud API or Twilio as a fallback, call it from Make.com or n8n via an HTTP request, and use approved message templates for notifications. This article explains how to send whatsapp notification end to end.

Why this happens: common roadblocks

People get blocked by three things: API choice and credentials, template approval and business verification, and implementation mistakes that produce delivery failures. Meta requires a verified business and approved message templates to send notifications outside the 24-hour user message window. Tokens expire or lack required scopes, and automation steps sometimes send wrong payloads or wrong headers, producing 401 or 403 responses.

how to send whatsapp notification: step-by-step fix

Pick API. Start with WhatsApp Business Cloud API if you want the cheapest path and full feature set, use Twilio Programmable Messaging if you prefer managed phone number handling and easier fallbacks.
Prepare business assets. In Meta Business Manager confirm your Business Manager ID, verify your business, add a WhatsApp Business Account, and register a phone number or use a phone number ID from your Cloud account. In Twilio verify your WhatsApp sender profile and sandbox or paid number.
Create and get templates approved. In Meta Business Manager open Message Templates and submit the template text, language and optional header. Only approved templates can be used for proactive notifications. For order notifications include variables like customer name and order id in the template.
Build the automation. In Make.com create a scenario, add your trigger module (webhook, Shopify, ClickUp), then add an HTTP module to call the chosen API. In n8n use a trigger node, transform data with the Code node if needed, then use the HTTP Request node to POST the message payload.
Set headers and body. Use an Authorization header with a Bearer token, and Content-Type application/json. For WhatsApp Cloud API call the messages edge for your phone number ID. For Twilio set the From value to the WhatsApp-enabled Twilio number like whatsapp:+ and the To value similarly.
Test in small batches. Send to test numbers first, then move to live. Monitor the response body and message status to detect template rejections, 403s, or rate limits.
Add retries and fallback. If WhatsApp Cloud API returns an auth or delivery error, route the scenario to a Twilio HTTP call or an SMS fallback, and log failures to a sheet or ticket system.

Make.com and module settings for WhatsApp

In Make.com build a scenario with these practical steps:

Create a Scenario and add your incoming trigger, for example a webhook or a Shopify module.
Add an HTTP module. Set Method to POST, URL to your chosen API messages edge. Under Headers add Authorization as Bearer YOUR_ACCESS_TOKEN and Content-Type as application/json.
In the HTTP module body use raw JSON and map fields from the trigger. Use Make.com tools like the JSON functions to build the template components safely.
Enable error handling on the HTTP module: right click the module, choose Error handlers, add a route to retry on 5xx and send a fallback via Twilio or SMS on persistent 4xx.

There are community threads showing Make.com implementations and patterns, for example this post about sending WhatsApp notifications from a restaurant site and another about building order updates from ClickUp, which are useful reference patterns.

Make community: send WhatsApp notification for orders

n8n notes for a WhatsApp support agent and notifications

n8n is useful for AI support agents and multilingual flows. Use the following nodes and settings:

Trigger with Webhook or scheduler.
Transform data with the Code node when you need to build complex JSON components for template placeholders.
Send the request with the HTTP Request node, set Method to POST, Authentication to None if you use header auth, and add the Authorization: Bearer TOKEN header and Content-Type: application/json.
For AI replies use an OpenAI or ChatGPT node to generate text, then feed that into the template or into a session-based conversational flow. For multilingual agents include language detection before selecting template language.

For n8n implementations where users ask for an AI WhatsApp support agent, see the community request that outlines the use case and language needs.

n8n community: AI WhatsApp support agent request

Troubleshooting checklist most answers miss

403 Forbidden: usually a token or access scope problem, or Business Manager verification is incomplete. Check that the token belongs to the WhatsApp Business Account phone number and that your Business Manager is verified.
401 Unauthorized: token expired or wrong header format. Confirm header uses Authorization: Bearer YOUR_TOKEN.
Template not approved: response will indicate template errors. Use only approved templates for proactive messages.
24-hour window rules: user-initiated messages can be replied to within 24 hours without templates. Proactive notifications need templates and approval.
Delivery failures: inspect message status in the API response or Webhook callbacks. Common states are sent, delivered, and failed. Log failures and add a retry with exponential backoff.
Signatures and security: if you use webhooks set up app secret verification so you only accept callbacks you can verify; in n8n/Make.com validate signatures before processing.
Rate limits: build graceful 429 handling and backoff. Log each rate limit event and notify an operator after multiple events.

When to get help and what to include

If you hit persistent 403 or template rejection after verification, raise a support ticket with Meta or Twilio. When asking for help include:

Exact response body and HTTP status code.
Screenshot or copy of the message template and its approval status.
Automation logs showing the exact request payload and headers with the token redacted.
Steps you took in Meta Business Manager or Twilio console and the phone numbers involved.

Small example headers and payload pattern

Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json

{
  "messaging_product": "whatsapp",
  "to": "whatsapp:+2348012345678",
  "type": "template",
  "template": { "name": "order_update", "language": { "code": "en_US" }, "components": [] }
}

Replace the phone number and template name with your values. Use the HTTP Request node in n8n or the HTTP module in Make.com to send this payload. If the API rejects the template, the response will indicate the reason.

Want a practical checklist to debug your Make.com outreach flows? See our Make.com outreach automation debug checklist for related troubleshooting patterns and logging tips.

Make.com outreach automation debug checklist

Automate Naija teaches hands-on automations with Make.com, n8n and AI. Learn to build reliable WhatsApp notification automations and fallbacks with us at Automate Naija.

Frequently asked questions

Can I send WhatsApp messages from Make.com without business verification?

You can send messages in the 24-hour conversation window for user-initiated chats without templates, but for proactive notifications you need approved message templates and usually a verified Meta Business. For full production reliability get your business verified and templates approved.

Should I use WhatsApp Cloud API or Twilio for notifications?

Use WhatsApp Cloud API for direct access and lower cost, use Twilio if you want Twilio features like managed number handling and easier fallbacks. Many teams implement Cloud API first and keep Twilio as a fallback when delivery or provisioning issues occur.

Why do messages show 403 or template errors?

403 often means the access token, phone number ID or business verification is incorrect. Template errors occur when you use a template that is not approved or has misformatted components. Check the API response body, and confirm template approval in Meta Business Manager.

How do I test WhatsApp notifications safely?

Use a small pool of test numbers, send only approved templates, and log every API response. Add retries for transient errors and a fallback route to Twilio or SMS for critical notifications. Record request payloads and response bodies for debugging.

Build it with us. The community is free and the build track teaches this kind of automation week by week: see pricing or join the community.