Integrations

Connect WhatsApp to Zapier and Make

Send and receive WhatsApp messages in Zapier or Make using webhooks and a plain HTTP action. No custom app to install and no per message fees.

Last updated 2026-08-02

Zapier and Make both speak plain HTTP, which is all wasender.dev needs. Sending a WhatsApp message is a Webhooks action, receiving one is a Catch Hook trigger, and there is no private app to get approved before you can start.

The same steps work in Make, substituting the HTTP module and the Custom Webhook module.

Before you start

Create a channel in the dashboard, copy the token, then fetch and scan the QR code:

curl https://api.wasender.dev/users/login/image \
  -H "Authorization: Bearer $WASENDER_TOKEN" \
  --output qr.png

Scan it in WhatsApp under Settings, Linked devices, Link a device. Your first number is free permanently, so there is nothing to pay to try this.

Send a WhatsApp message from a Zap

Add a Webhooks by Zapier action, choose POST, and fill in:

• URL: https://api.wasender.dev/messages/text
• Payload Type: JSON
• Data: to set to the recipient number, body set to your message
• Headers: Authorization set to Bearer wsk_sg_your_token_here, and Content-Type set to application/json

Numbers go in international format without a leading +, so 61371989950 rather than +61 371 989 950. If your trigger app stores numbers with a plus or with spaces, add a Formatter step to strip them first. This is the single most common reason a Zap runs green but no message arrives.

In Make, the equivalent is an HTTP, Make a request module with the same URL, method, headers and a JSON body.

Receive WhatsApp messages into a Zap

Create a Zap with the Webhooks by Zapier trigger, choose Catch Hook, and copy the URL it gives you. Register it against your channel:

curl -X PATCH https://api.wasender.dev/settings \
  -H "Authorization: Bearer $WASENDER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "webhooks": [
      {
        "url": "https://hooks.zapier.com/hooks/catch/000000/abcdef",
        "events": [{ "type": "messages", "method": "post" }],
        "mode": "body"
      }
    ]
  }'

You can also set the webhook URL from the dashboard.

Now message your connected number. Zapier captures the delivery and shows you the payload, which is the shape your later steps should reference. Read it from that real sample rather than copying field names out of a guide.

Subscribe to statuses as well if you want delivery and read receipts. The available event types are messages, statuses, chats, contacts, groups, calls and users.

Zaps worth building

New order, send a WhatsApp confirmation. Shopify or WooCommerce trigger into a Webhooks action.

New booking, send a reminder. Calendly or Google Calendar trigger, a Delay step, then the message.

Form submitted, start a conversation. Typeform or Google Forms into a first reply, then let a human take over in WhatsApp.

Incoming message, create a ticket. Catch Hook trigger into Zendesk, HubSpot or a spreadsheet.

Incoming message, answer with AI. Catch Hook, then a ChatGPT step, then a Webhooks action to send the reply back.

Beyond text

Change the URL and the same action sends anything: /messages/image, /messages/video, /messages/document, /messages/location, /messages/contact and /messages/poll all take the same auth header and a JSON body. Group administration and contact checks work the same way. The full list is in the API reference.

Troubleshooting

The Zap succeeds but nothing arrives. Check the recipient format first. A 2xx means WhatsApp accepted the message, not that it was delivered, so confirm with GET /statuses/{MessageID}.

401 Unauthorized. The header must read Bearer followed by the whole wsk_ token. A trailing space or a truncated paste is usually the cause.

429 Too Many Requests. Rate limits protect your number from WhatsApp's anti abuse systems. Add a Delay step rather than retrying immediately.

503 Service Unavailable. The session is reconnecting. Retry with backoff.

Costs

There are no per message or per task fees on our side. The first connected number is free permanently and each additional number is a flat $4 a month, so a Zap firing once a week and one firing every minute cost the same.

A note on which number to use

This drives WhatsApp through an unofficial client, the same mechanism WhatsApp Web uses. Meta does not sanction it, so use a dedicated number rather than your main business line, and do not send first contact messages to people who never opted in. For regulated workloads, use Meta's official Cloud API instead.

Back to all articles