Send WhatsApp Messages with n8n (HTTP Request Guide)
Any statistics or percentages in this article are general industry figures or illustrations, not QuackAPI measurements or promises. Results depend on your audience, consent and sending patterns. QuackAPI connects to WhatsApp as a linked device (an unofficial method), so read our risk and acceptable use policy before sending.
Do you need a special n8n node?
No. n8n can call any REST API with its built-in HTTP Request node, and QuackAPI is a plain REST API: one POST request with a JSON body and an API key header. That means you can send WhatsApp messages from any n8n workflow, on n8n Cloud or self-hosted, without installing a community node.
This guide builds three small workflows: send a message, send a message for every new row or incoming webhook, and receive WhatsApp replies in n8n. It also covers retries and pacing so a long run does not trip over its own limits.
Only message people who have agreed to hear from you. QuackAPI is a linked-device service, not Meta's official Cloud API, so WhatsApp can restrict a number it considers abusive. Read the acceptable use policy before you automate anything.
What you need first
A QuackAPI account with a connected device, the device's numeric id (from the device page URL) and your API key, which starts with wa_. Keep the key out of workflow JSON: you will store it as an n8n credential in the next step.
Step 1: Create a credential for the API key
In n8n open Credentials, choose Create credential and pick Header Auth. Set Name to x-api-key and Value to your wa_ key. Give the credential a clear name such as QuackAPI.
Using a credential rather than typing the key into the node means the key is encrypted by n8n, is not exported when you share a workflow, and can be rotated in one place.
Step 2: Send a message with the HTTP Request node
Add an HTTP Request node and configure it like this. Method: POST. URL: https://quackapi.com/v1/messages/chat. Authentication: Generic Credential Type, then Header Auth, then choose the QuackAPI credential. Turn on Send Body, set Body Content Type to JSON, and use the JSON field below.
The two expressions read the phone number and text from the previous node. Change the field names if your data uses different ones.
{
"deviceId": 1,
"to": "{{ $json.phone }}",
"body": "{{ $json.message }}"
}What the response looks like
A successful call returns HTTP 200 with a small JSON object. Status queued means QuackAPI accepted it and will send it. Whether it was actually delivered arrives later as a webhook event.
{
"success": true,
"messageId": 1042,
"status": "queued"
}Workflow 1: Send a message when a webhook is called
The most common pattern is another system telling n8n that something happened, such as a new order. Add a Webhook node as the trigger (method POST), then connect the HTTP Request node from Step 2. Your shop or app sends JSON such as {"phone":"923001234567","message":"Your order has shipped"} to the webhook URL, and n8n turns it into a WhatsApp message.
n8n gives each Webhook node a Test URL and a Production URL. The test URL only works while you are listening in the editor. Activate the workflow and use the production URL in your other system.
Workflow 2: Send to a list without overloading the number
If the trigger produces many items at once (for example a Google Sheets node that reads 200 rows), the HTTP Request node will fire for every item immediately. Do not do that. Insert a Loop Over Items node with a batch size of 1, then a Wait node of a few seconds after the HTTP Request, and connect it back to the loop. This sends one message at a time with a pause between them.
Pacing matters for the health of your WhatsApp number. Sending many messages to many different people in a burst is the pattern WhatsApp's systems flag. See the guide on avoiding a WhatsApp number ban for what to watch for.
Handle errors and retries
Open the HTTP Request node Settings. Turn on Retry On Fail with 3 tries and a wait of a few seconds between them. This covers short outages and a 409 device not ready response while a session starts up.
Set On Error to Continue (using error output). The node then has a second output for failed items, where you can write the problem to a spreadsheet, send yourself an alert, or stop the workflow. Some errors should not be retried. A 400 means the request itself is wrong, a 401 means the key is wrong, and a 429 means you hit the plan's daily limit.
| HTTP status | Meaning | Retry? |
|---|---|---|
| 200 | Accepted and queued | No |
| 400 | Validation error, the message names the field | No, fix the data |
| 401 | API key missing or invalid | No, fix the credential |
| 403 | Account suspended, or the device is disconnected or disabled | No, reconnect the device |
| 404 | Device not found | No, check deviceId |
| 409 | Device is not ready yet | Yes, after a pause |
| 429 | Daily message limit reached | Not today |
Workflow 3: Receive WhatsApp replies in n8n
To react to incoming messages, create a workflow that starts with a Webhook node (method POST) and copy its production URL. In QuackAPI open the device, paste that URL as the webhook URL and save. When someone writes to your number, QuackAPI sends a JSON POST with the event name message.received, the device id, the sender number in from, the text in content, a timestamp and a messageId.
Add an IF node that checks the text, for example whether {{ $json.body.content }} equals STOP, and branch: for STOP, add the number to your opt-out list and send nothing more; for anything else, notify your team or reply with another HTTP Request node. The webhook body arrives under the body key in n8n.
Webhooks are not signed today, so treat the URL as a secret, validate the fields you depend on and use messageId to avoid processing the same event twice. The webhook reference lists every event and field.
Send a document or an image from n8n
Media works the same way with a different URL. For a PDF use https://quackapi.com/v1/messages/document and a body with deviceId, to, document (a public URL to the file) and an optional filename. For a picture use /v1/messages/image with an image URL and an optional caption. The file must be reachable by QuackAPI, so use a link that works without logging in, ideally an expiring signed link for anything private.
{
"deviceId": 1,
"to": "{{ $json.phone }}",
"document": "{{ $json.invoice_url }}",
"filename": "invoice-{{ $json.order_id }}.pdf"
}Make and Zapier work the same way
Everything above carries over to other automation tools. In Make use the HTTP module (Make a request), and in Zapier use Webhooks by Zapier with a POST action. Add the x-api-key header, set the body type to JSON and send the same fields. The only difference is the interface.
Frequently asked questions
Is there an official QuackAPI n8n node?
Can n8n trigger a workflow when I receive a WhatsApp message?
How many messages can n8n send per minute?
Does this need the WhatsApp Business API or message templates?
Where to go next
See the n8n integration page for a short summary, the API quick start for all request fields, and send WhatsApp messages from Google Sheets if your data already lives in a spreadsheet.