Evolution API + n8n for WhatsApp: Self-Host or Use an Official Provider?
The decision in plain English
Evolution API can put a useful REST layer in front of WhatsApp, and n8n can handle the logic around it. The part people skip is which WhatsApp connection sits underneath.
Evolution's own documentation says it supports both a Baileys-based WhatsApp connection and the official WhatsApp Business API. Those are not interchangeable routes. A QR-connected Baileys session is attractive for prototypes and self-hosted experiments. The official business route is the more defensible choice for a customer-facing operation that needs approved templates, documented opt-ins, predictable account ownership, and provider support.
If one missed message costs the business a sale, choose the connection model before drawing the workflow.
A sensible n8n architecture
Keep n8n responsible for orchestration, not for pretending a message was delivered:
lead source → n8n webhook → validate and deduplicate → WhatsApp API/provider → delivery callback → CRM or database
The return path matters as much as the send:
customer reply → provider webhook → n8n → match contact → notify the right person → log outcome
Build five controls from day one:
- Idempotency: give each lead event a stable ID so retries do not send duplicate messages.
- Consent record: store where and when the person opted in, plus the wording they saw.
- Template state: do not treat a draft template as approved or available in every language.
- Delivery callbacks: record sent, delivered, read, failed, and the provider error rather than trusting an HTTP 200 from the first request.
- Human handoff: once a person replies or asks for help, stop the automation that would talk over the agent.
Option 1: Evolution API with a Baileys session
This route appeals to developers because it is open-source, self-hostable, and quick to connect with a QR code. It can be reasonable for learning, an internal lab, or a low-stakes prototype.
The trade-off is operational responsibility. You own the server, database, updates, session persistence, reconnect behavior, monitoring, backups, and every edge case after a phone or session changes. More importantly, a Baileys-based connection is not the same product as Meta's official Cloud API. Do not sell it to a client as though those words mean the same thing.
Before using it with real customers, answer:
- Who restores the session after a disconnect?
- What happens to inbound messages while it is offline?
- How are secrets and message data encrypted and backed up?
- Can the business export the number, contacts, templates, and logs without you?
- What is the rollback plan if an update breaks the connector?
If those questions feel bigger than the automation itself, a managed official provider is probably cheaper than self-hosting once your time is counted.
Option 2: Evolution API with the official WhatsApp Business API
Evolution documents support for the official WhatsApp Business API as a separate integration path. This can preserve a self-hosted orchestration layer while keeping the WhatsApp connection in the official business channel.
It is still not maintenance-free. You must configure Meta business assets, phone-number ownership, access tokens, webhooks, templates, permissions, and the current messaging charges. Read Meta's current rules at implementation time; pricing and message categories can change.
Use the WhatsApp cost calculator with the current Meta rate for the recipient country. A platform subscription and Meta's message charge are separate lines in the budget.
Option 3: use n8n with a managed official provider
For a sales or support team, this is usually the quickest route to a shared inbox, template management, agents, routing, and human handoff. You give up some infrastructure control and pay a subscription, but the business gets an interface it can operate without opening Docker logs.
Two StackPick partner options are:
Gallabox
Gallabox is the better shortlist candidate when the team wants WhatsApp, Instagram, a web inbox, multi-user handling, and packaged automation in one product. Confirm the current plan, user limits, AI allowances, and Meta charges before buying.
Check Gallabox through StackPick →
AiSensy
AiSensy is the more focused shortlist candidate for budget-conscious WhatsApp broadcasts, simple chatbot flows, and a shared operating layer on the official API. Verify current local pricing, taxes, included features, and message charges on its own page.
Check AiSensy through StackPick →
Affiliate disclosure: Gallabox and AiSensy are active StackPick partner links. StackPick may earn a commission if you purchase through them, at no extra cost to you. Evolution API and n8n are discussed on their merits; StackPick currently has no active commissioned n8n link.
Which route should you choose?
| Situation | Better starting point |
|---|---|
| Learning or disposable prototype | Evolution API with a Baileys session, isolated from a critical number |
| Technical team wants self-hosting but needs the official business channel | Evolution API's official WhatsApp Business API path |
| Small business needs an inbox and human handoff quickly | Managed provider such as Gallabox or AiSensy |
| Agency serving several clients | Official provider or official API path with explicit ownership, monitoring, and per-client isolation |
| High-cost missed leads or regulated data | Official route, documented consent, tight access controls, and a tested fallback |
The best architecture is not the one with the fewest subscription fees. It is the one the business can still operate on a Friday night when a token expires, a webhook retries, or the person who built it is unavailable.