WhatsApp has no "connect to n8n" button. To send and receive messages from a workflow you need a WhatsApp API: a service that holds the connection to a number and exposes it over HTTP so n8n can call it and be called by it. Evolution API is the open-source one most self-hosters use; the other route is Meta's official WhatsApp Business Platform. This guide walks through the Evolution API route and says plainly where it stops being the right choice.
What Evolution API is
Evolution API is an open-source server that connects to WhatsApp the way WhatsApp Web does: you scan a QR code with the phone that owns the number, and from then on the server can send and receive messages on that number through a REST API and webhooks. It runs as a Docker container with a Postgres database, needs a domain with SSL, and is the kind of thing RinooSol hosts as a private WhatsApp API instance: your own container, subdomain, certificate and backups, ready to connect to n8n.
Because it connects like WhatsApp Web, it works with an ordinary number, needs no business verification and carries no per-message fee. It is also not sanctioned by Meta, which is the trade-off the last section is about.
What you need before you start
- A number dedicated to automation. It can be a SIM in a spare phone. Do not use the owner's personal number: the first time a flow misbehaves you will want to unplug it without losing your own WhatsApp.
- A running Evolution API instance with a URL and an API key. On a managed instance both are in your dashboard; self-hosting means a VPS, Docker, Postgres, a reverse proxy and a certificate first.
- An n8n instance that can reach the API over the internet, and that the API can reach back with webhooks. A managed n8n plan and a managed Evolution API instance already satisfy both.
Step 1: connect the number
In the Evolution API panel, create an instance (their word for one connected number), open its QR code, and on the phone go to WhatsApp → Linked devices → Link a device, then scan. The instance status changes to connected. Keep the phone charged and online for the first day; after the session is established it can be offline for stretches, but a phone that is off for weeks will eventually need a new scan.
Step 2: send a message from n8n
In n8n, add an HTTP Request node:
- Method
POST, URLhttps://<your-instance>/message/sendText/<instance-name> - Header
apikey: <your API key> - JSON body
{"number": "2010XXXXXXX", "text": "Hello from n8n"}
Numbers are international format without the plus sign. Run the node once by hand and check the phone receives it. There is also a community node package for Evolution API in n8n's community nodes; it wraps the same endpoints with a form instead of a JSON body, and is worth installing once the first manual call works.
Step 3: receive messages with a webhook
In n8n, add a Webhook trigger, copy its production URL, and in Evolution API set the instance's webhook URL to it with the messages upsert event enabled. Send a message to the number from another phone; the trigger fires with a JSON body containing the sender, the text and the message id. Everything downstream is ordinary n8n: an if on the text, a lookup in a sheet, a reply with the HTTP node from step 2.
Two details that save an afternoon:
- Evolution API sends you your own outgoing messages as well, flagged
fromMe: true. Filter them out first or every reply triggers the workflow again. - A group message carries a group id instead of a number. Decide early whether your flow should ignore groups; most should.
Step 4: the handover to a person
Every flow needs a door. The simplest: a keyword such as "agent" or anything the workflow does not recognise sets a flag in your sheet or CRM for that number, notifies a person, and the workflow stays silent for that number until the flag is cleared. Without this, a customer who asks a real question gets an automatic reply in the middle of a real conversation, which is worse than no automation.
The rules, honestly
WhatsApp's terms do not allow bulk unsolicited messaging, and a number that sends a lot of first-contact messages to people who never wrote to it gets restricted, sometimes permanently. Evolution API will not stop you; the restriction is the stop. Build flows around people who wrote to you first, or who gave you their number for exactly this message (a booking confirmation, an order update, a reminder for an appointment they made). Keep the volume human-shaped, and never upload a purchased list.
When the official API is the better route
Meta's WhatsApp Business Platform is the sanctioned API: a verified business name, approved message templates for anything sent outside a 24-hour conversation window, per-conversation pricing and no restriction risk from the channel itself. It takes longer to set up (a Meta business account, verification, template approvals) and n8n supports it with a built-in node. Choose it when you will send notifications at scale to customers who did not message you first, when a verified green badge matters to your customers, or when the number is one the business cannot afford to lose. For a reply-driven flow at modest volume, Evolution API is faster and cheaper; for customer-facing notifications at scale, the official platform is the safer system. RinooSol builds on either and chooses the route with you in the consultation.
What a finished setup looks like
A clinic's number connected to a private Evolution API instance; an n8n workflow that answers the five common questions, confirms bookings from the calendar, reminds patients the evening before and hands anything else to the reception. The WhatsApp automation page describes that build step by step, and the appointment reminders page the reminder part on its own.