Anyone Here Using Evolution API with n8n? Thinking of Switching from Waha

Questions
1

I’m getting tired of Waha—it keeps running into timeout errors over and over again. I’ve restarted it multiple times, and sometimes I even have to fully reinstall it. Not just restart or redeploy, but actually delete everything and set it up again from scratch.

So now I’m thinking about switching to Evolution API (or maybe WasenderAPI, but I’m leaning toward Evo since it already has a community node).

Has anyone here used Evolution API with n8n? What’s your experience been like? Would you recommend it in terms of cost and stability? I’d really appreciate any insights.

And for those wondering why I’m not using the official Meta API: I don’t have the required legal documents to register, and I’m based in a developing country where the pricing is relatively expensive—especially for small businesses.

  • n8n version: self hosted v2.1.5
  • Database (default: SQLite): Postgres
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker (Deploy Coolify)
  • Operating system: Ubuntu v22.04 VPS
3

@bytegir switch to Evolution API, it’s way more stable than Waha and the community node works solid with n8n. here’s a basic webhook receiver for evo messages coming into n8n:

drop your evo instance URL and apikey into the Reply node, set the webhook URL in your Evolution API instance settings to point at the webhook path

4

WasenderAPI also has a community node and its pretty great it handle web hook and everything for you