Automation · n8n
n8n WhatsApp Integration
Send WhatsApp messages from an n8n workflow using the Wasaas REST API. There is no dedicated community node published yet — this page shows the HTTP Request node setup that works today, with the same requests a dedicated node would make.
Status: no published community node yet
A dedicated Wasaas node for n8n is in development and is not published to the n8n community nodes registry as of this writing. Nothing below depends on it — the HTTP Request node is a first-class way to call any REST API from n8n, and it reaches every endpoint a dedicated node would. We will update this page and link to the node directly once it ships.
The problem this solves
A lot of real automation work — order confirmations, appointment reminders, internal alerts — already lives in n8n as a workflow triggered by a form, a database change, a schedule or another app's webhook. The missing piece is usually the last step: getting a WhatsApp message out without writing or hosting a separate microservice just to call an API. An HTTP Request node pointed at Wasaas is that last step.
Set up the HTTP Request node
- Create a Wasaas account and connect a WhatsApp number (Sessions → Add Session, scan the QR code) to get a session ID.
- Create an API key in the dashboard, prefixed
wsa_. - In n8n, add an HTTP Request node anywhere a message should go out, configured as below.
| Method | POST |
| URL | https://wasaas.org/api/v1/messages |
| Authentication | Generic Credential Type → Header Auth. Name: Authorization, Value: Bearer wsa_your_api_key |
| Body (JSON) | session_id, to, message — see below |
Body, with values taken from earlier nodes in the workflow (n8n expression syntax):
{
"session_id": "customer-5-1",
"to": "{{ $json.phone }}",
"message": "{{ $json.text }}"
}The equivalent request outside n8n, for comparison — this is the exact call the node makes:
curl -X POST https://wasaas.org/api/v1/messages \
-H "Authorization: Bearer wsa_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"session_id": "customer-5-1",
"to": "966501234567",
"message": "Your appointment is confirmed for tomorrow at 10am."
}'Sending images, documents or bulk messages
The same HTTP Request pattern works against the other endpoints — swap the URL and body fields:
POST /api/v1/messages/image— image by URL, with an optional captionPOST /api/v1/messages/document— document as base64, with a filename and MIME typePOST /api/v1/messages/bulk— up to 500 recipients in one call, useful for an n8n node that loops over a spreadsheet or database query
Limitations — read before building a workflow around this
This is an unofficial, session-based WhatsApp integration, not Meta's official Business Platform — a connected number stays subject to WhatsApp's normal terms and spam enforcement. There is no trigger node for incoming messages: outbound webhook delivery from Wasaas to your n8n workflow's webhook URL is not implemented today, so a workflow can send WhatsApp messages but cannot currently start when one arrives. Supported message types are text, image and document; audio, location pins and interactive buttons are not available.
Pricing
Every plan includes full REST API access, which is all this integration needs. See WhatsApp API pricing for current session, message and API-call allowances, and start with the free trial before committing to a plan.
Where to go next
- WhatsApp REST API documentation — every field and error code the HTTP Request node can hit
- WhatsApp REST API — the full resource list this integration calls into
- WhatsApp API for developers — SDKs and the setup flow, if n8n isn't the only place you integrate
- WhatsApp bulk messaging API — pacing and quota behaviour for a workflow that fans out to many recipients