There are two ways to connect a WhatsApp number to an automation. One is sanctioned by Meta and comes with verification, templates and per-conversation pricing. The other is open-source, connects like WhatsApp Web, and comes with speed, a normal number and the risk that Meta restricts it. RinooSol builds on both and chooses with the customer; this guide is the comparison we walk through when we do.
The two in one paragraph each
The official WhatsApp Business Platform (often called the Cloud API) is Meta's own API. You create a Meta business account, verify the business, register a number that is not already on a personal WhatsApp, and get access tokens. Outbound messages to people who have not written to you in the last 24 hours must use a template Meta has approved. Pricing is per conversation, by category and country. n8n has a built-in node for it.
Evolution API is open-source software that connects to WhatsApp the way the WhatsApp Web client does. You run it (or rent a private instance), scan a QR code with the phone that owns the number, and the server exposes send and receive over REST and webhooks. Any number works, there are no templates and no per-message fees, and it is not sanctioned by Meta. The setup guide walks through it.
Side by side
| Evolution API (unofficial) | Official WhatsApp Business Platform | |
|---|---|---|
| Setup time | An hour, including the QR scan | Days to weeks: business verification, number registration, template approvals |
| Number | Any number, including one already on a phone | A number dedicated to the API, not on a personal WhatsApp |
| Cost | The hosting of the instance; no per-message fee | Per conversation, by category; free within some limits, then metered |
| Outbound rules | No template system; WhatsApp's general anti-spam rules apply | Templates required outside the 24-hour window; templates reviewed by Meta |
| Restriction risk | Real: aggressive sending gets the number restricted, sometimes permanently | None from the channel itself; abuse still breaks policy |
| Verified name and badge | No | Yes, after verification |
| Media, buttons, lists | Supported, with some features depending on the WhatsApp client behaviour | Supported through official message types |
| Groups | Can read and send in groups (against Meta's policy for automation) | Not supported |
| Reliability | Depends on the session staying linked; a phone off for weeks needs a re-scan | Meta's infrastructure |
| n8n integration | Community node and HTTP requests | Built-in node |
Where Evolution API is the right choice
- Reply-driven flows at modest volume. A clinic answering questions, a shop confirming orders to people who ordered, a reminder to someone who booked. The person wrote to you or gave you the number for this; the volume is human-shaped.
- Getting started this week. Verification and template approval on the official platform take time; a flow on Evolution API can be live today and move to the official platform later if it grows.
- A number you already use. The official platform needs a dedicated number; Evolution API can connect the number customers already know.
- Cost sensitivity at low volume. No per-conversation fee; the instance is a flat monthly cost.
Where the official platform is the right choice
- Notifications at scale to people who did not write first. Delivery updates to hundreds of customers a day, appointment reminders for a large clinic chain, payment reminders across a customer base. This is exactly what templates and the 24-hour rule are designed for, and exactly what gets an unofficial number restricted.
- A number the business cannot afford to lose. A restriction on an unofficial instance is sudden and sometimes final. If the number is on the shop front, go official.
- A verified name and badge. Customers who see a verified business name trust the message more, and some industries expect it.
- Compliance obligations. If someone will ask "is this sanctioned by Meta?", the answer needs to be yes.
The rule we use
Ask two questions. Will this number send to people who did not write to it first, at any real volume? If yes, official. Is losing this number a business problem? If yes, official. If both answers are no, Evolution API gets you running faster and cheaper, and you can move the flow to the official platform later; the n8n workflow is the same, only the sending node changes.
Running both
Some customers run both: an Evolution API instance on a secondary number for reply-driven conversation flows, and the official platform on the main number for notifications. The workflows are shared; n8n does not care which door a message goes through. We set this up when a customer's mix of traffic calls for it, and we say so in the consultation rather than selling one route to everyone.