Platform
Chatbot Builder Bulk Messaging Team Inbox Mini CRM API & Webhooks AI Integration WhatsApp Flows
Industries
E-commerce & D2C Real Estate Education Healthcare Finance & BFSI Logistics Hospitality Retail
Integrations
Learn
Learning Hub Help & Docs Connect Guides Automation Codex Blog Message Templates
Pricing Start Free Trial →
HomeConnect › Connect Make to WhatsApp
Make Integration Guide · iPaaS / Automation

Connect Make to WhatsApp

Make (formerly Integromat) connects 3,000+ apps through a visual canvas builder. Use Make's HTTP module to call WA.Expert and trigger WhatsApp messages from any scenario, cheaper than Zapier for complex workflows, with webhooks free on all plans.

Published 23 June 2026  ·  7 min read  ·  iPaaS / Automation
Make uses the HTTP module to call WA.Expert: no native app needed

Unlike Zapier, Make does not have a native WA.Expert app. Instead, add an HTTP → Make a Request module to your scenario and call the WA.Expert API directly. This works on all Make plans including the free tier and gives you full control over every parameter.

Make webhooks are free: an advantage over Zapier

Make's Custom Webhooks are available on every plan at no extra cost. In Zapier, Webhooks by Zapier requires a paid plan. This means receiving WhatsApp reply data into a Make scenario costs nothing extra.

Make vs Zapier for WhatsApp automation

MakeZapier
WA.Expert native appNo: use HTTP moduleYes: native app
Webhooks (receive data)Free on all plansPaid plan required
Free plan1,000 ops/month100 tasks/month
Paid plan entry$9/month (10,000 ops)$20/month (750 tasks)
Complex multi-stepMore affordableCosts more per run
Visual builderCanvas (node graph)Linear list
Best forComplex scenarios, more ops neededSimple 2-step Zaps, broad app library

1 Make operation = 1 module execution. A 3-module scenario uses 3 ops per run. Zapier charges 1 task per full Zap run regardless of step count.

Direction 1: App trigger fires a WhatsApp via WA.Expert

Step 1: Create the scenario

1
In make.com, click Create a new scenario.
2
Click the + to add the first module. Search for your trigger app (Google Sheets, Typeform, Shopify, Calendly, etc.) and select the event.
3
Connect your account and configure the trigger. Click Run once to fetch sample data from the trigger.

Step 2: Add the HTTP module

1
Click + after the trigger module. Search for HTTP and select Make a Request.
2
Configure the HTTP module as shown below.
HTTP module configuration in Make
URL:     https://YOUR-DOMAIN.wa.expert/v1/messages
         (your WA.Expert domain from Settings)

Method:  POST

Headers:
  API-KEY: YOUR_WAEXPERT_API_KEY
  Content-Type: application/json

Body type:    Raw
Content type: JSON (application/json)

Request content:
{{
  "to":       "{{1.phone_number}}",
  "type":     "template",
  "template": {{
    "name":     "order_confirmation",
    "language": {{"code": "en"}},
    "components": [
      {{
        "type": "body",
        "parameters": [
          {{"type": "text", "text": "{{1.customer_name}}"}},
          {{"type": "text", "text": "{{1.order_id}}"}}
        ]
      }}
    ]
  }}
}}

{{1.phone_number}} = mapped from the trigger module's phone field
{{1.customer_name}} = mapped from the trigger module's name field
Find your WA.Expert API key and domain

In WA.Expert, go to Settings → API Keys for the API key. Your domain is the subdomain of your WA.Expert account, shown in the Settings panel. Use https://YOUR-DOMAIN.wa.expert/v1/messages as the endpoint.

Step 3: Test and activate

1
Click Run once to execute the scenario once with the sample data.
2
Check the HTTP module's output. A Status: 200 response confirms the WhatsApp was sent. Verify delivery in WA.Expert's message logs.
3
Click the Scheduling toggle to activate the scenario. Set it to run immediately when new data appears (instant trigger).

Direction 2: WhatsApp data triggers a Make scenario

Receive WhatsApp reply data into Make to update a CRM, log to a spreadsheet, or trigger any downstream action.

1
In Make, create a new scenario. Add a Webhooks → Custom webhook module as the trigger. Click Add, name the webhook, and copy the generated URL.
2
In WA.Expert, add an External API Request step to your automation. POST the customer data to the Make webhook URL.
3
Back in Make, click Run once and trigger the WA.Expert automation to send a test payload. Make captures the data structure automatically.
4
Add action modules after the webhook: Google Sheets, HubSpot, Airtable, Slack, etc. Map the payload fields to the module inputs.
WA.Expert External API Request — POST to Make webhook
POST https://hook.eu2.make.com/YOUR_WEBHOOK_ID
Content-Type: application/json

Body:
{{
  "customer_name":    "{{customer_name}}",
  "customer_phone":   "{{customer_phone}}",
  "customer_message": "{{customer_message}}",
  "timestamp":        "{{timestamp}}"
}}

Make receives this and routes it through your scenario:
  Webhook -> Google Sheets (append row)
  Webhook -> HubSpot (update contact)
  Webhook -> Slack (notify team)

Worked example: Typeform submission to WhatsApp

Make scenario — Typeform new submission to WhatsApp confirmation
Modules in the scenario:

1. Typeform — Watch Responses (trigger)
   Form: Lead Enquiry
   Trigger on: new submission
   Sample data received:
     1.answers[0].text = 'Priya Sharma'  (name)
     1.answers[1].phone_number = '+919820000001'
     1.answers[2].email = 'priya@example.com'

2. HTTP — Make a Request
   URL: https://yourdomain.wa.expert/v1/messages
   Method: POST
   Headers: API-KEY: YOUR_KEY
   Body:
   {{"to": "{{1.answers[1].phone_number}}",
     "type": "template",
     "template": {{"name": "lead_confirmation",
       "language": {{"code": "en"}},
       "components": [{{"type": "body",
         "parameters": [{{"type": "text",
           "text": "{{1.answers[0].text}}"}}]
       }}]
     }}
   }}

3. Google Sheets — Add a Row (optional logging)
   Sheet: Leads
   Name: {{1.answers[0].text}}
   Phone: {{1.answers[1].phone_number}}

Total operations per run: 3 (one per module)
Free plan: handles ~333 Typeform submissions/month

Troubleshooting

SymptomLikely causeFix
HTTP module returns non-200Wrong URL or API keyCheck the WA.Expert domain and API key in the HTTP module headers. Test the URL independently with the API key to confirm it is valid.
Template not foundTemplate name wrong or not approvedEnsure the template name in the JSON body matches the approved template in WA.Expert exactly. Templates must be approved by Meta before use.
Phone number not mappedWrong field path from triggerUse Make's mapping panel to select the correct field. The field path depends on the trigger app's data structure.
Scenario not running automaticallyScheduling not activatedAfter testing, click the Scheduling toggle to turn the scenario on. Also check the trigger module is set to instant (webhook) or a schedule.
Operations running outHigh submission volume on free planFree plan: 1,000 ops/month. A 2-module scenario: 500 submissions. Upgrade to Core ($9/month, 10,000 ops) for higher volume.
Webhook not receiving dataWrong Make webhook URL in WA.ExpertCopy the full Make webhook URL (hook.eu2.make.com/... or hook.us2.make.com/...) and confirm it is pasted exactly into the WA.Expert External API Request step.

Common questions

Does Make have a native WA.Expert app?
+
No. Use the HTTP Make a Request module to call the WA.Expert API directly. Available on all plans including free.
How is Make different from Zapier?
+
Make charges per operation (module execution), not per Zap run. Cheaper for complex multi-step scenarios. Webhooks are free on all plans. Visual canvas builder vs Zapier's linear list.
Are Make webhooks free?
+
Yes. Custom Webhooks are available on every Make plan at no extra cost. Contrast with Zapier where Webhooks by Zapier requires a paid plan.
What is a Make operation?
+
One module execution = 1 operation. A 3-module scenario uses 3 ops per run. Free plan: 1,000 ops/month. Core: 10,000 ops/month at $9/month.
Can I receive WhatsApp data into Make?
+
Yes. Add a Custom Webhook module as trigger to get a URL. POST to that URL from WA.Expert's External API Request step. Free on all plans.
Does this incur extra WA.Expert charges?
+
Each WhatsApp uses a message credit. Utility: Rs. 0.14 on Starter. Make charges operations: 1 per module per run.

Connect Zapier to WhatsApp

Zapier: native WA.Expert app, 7000+ triggers, simpler setup.

Read guide →

Connect n8n to WhatsApp

n8n: open-source, self-hosted option, no per-operation costs.

Read guide →

External API Request Step

Master every field in WA.Expert's HTTP action step.

Read foundation guide →

Connect Make to WhatsApp today

Free trial, no credit card. If you get stuck, we answer live on WhatsApp.

Start Free Trial → Book a Demo
1