If you're building a side project or a bootstrapped SaaS and you want to plug WhatsApp into your stack without paying $99/month before you have a single paying user — this post is for you.
I've burned more hours than I'd like to admit on "free" WhatsApp tools that turned out to be 7-day trials with hidden seat-based pricing. So I sat down, tested everything I could find, and pulled together this list of tools that are actually free (or have a usable free tier) for indie hackers in 2026.
TL;DR — if you want the shortest path: start with Wappfly. If you want maximum control: self-host Evolution API. Everything else on the list is a specialty pick.
There are three categories worth separating:
I weighted the list toward the first and third. Trials are noted, but I don't trust them for long-term builds.
Wappfly is where I send most people who DM me asking "how do I add WhatsApp to my MVP this weekend?"
The free plan covers what an indie hacker actually needs: text messages, images, photos, document attachments (PDF, Word, Excel) — and most importantly, receiving messages and replying to them. That last bit is what makes it usable for real two-way flows, not just one-way notifications.
What I like:
What's missing:
If you're a one-person shop and just need WhatsApp working this week, this is the lowest-friction option on the list.
Open source. Self-hosted. Free forever if you have a $5/mo VPS lying around.
Evolution API is the indie hacker's dream if you don't mind a docker-compose up. You get the full WhatsApp Web protocol exposed as REST endpoints plus webhooks. n8n integration is just HTTP Request nodes pointing at your own server.
The tradeoffs are real, though: you're responsible for keeping it running, it uses unofficial WhatsApp Web (so not great for high-volume commercial use), and setup eats an afternoon if you've never touched Docker.
But the freedom is also real. No vendor, no rate limits except WhatsApp's own.
Meta hands out 1,000 free service conversations per month. For most early-stage projects, that's plenty.
It's the official API, so you get the Green Tick path and you're not worried about your number getting banned overnight. The downside: setup is a multi-step Meta Business Verification dance that will eat half a day and require you to find your business documents.
Pair it with n8n's built-in WhatsApp Business node and you're done.
Baileys is a TypeScript library, not a service. If you're a developer who wants zero vendor dependencies, Baileys is the cleanest WhatsApp Web library on GitHub. Spin up a Node process, scan a QR, and you have full programmatic access to WhatsApp.
Free in the truest sense — it's a library. You write the code. You own the loop.
Open source like Baileys, but with more out-of-the-box features — multi-device, session management, a REST wrapper. Built and maintained by a Brazilian community.
If Baileys is too low-level and Evolution API feels too heavy, WPPConnect sits comfortably in the middle.
Another open-source Node.js library for WhatsApp Web. Solid for small bots, decent docs, but the development pace has slowed. Still a fine pick for hobby projects and weekend hacks.
Chatwoot is open-source customer support software. The self-hosted version is completely free, and it has a WhatsApp channel that plugs into 360dialog or WhatsApp Cloud API.
Not strictly an automation tool — but if you want a shared inbox plus automation rules without paying Intercom money, this is it. Combine with n8n for triggers and you have a poor man's Front for free.
A cloud-based service with a free developer plan: low message volume, perfect for prototyping. Once you go past prototype usage, the paid plans kick in.
Uses unofficial WhatsApp Web. Easy QR setup. Good docs. Fine for hobby bots.
Free trial, not a permanent free tier — but the trial gives you enough to ship an MVP and validate before paying anyone. Cheapest paid plans on the list after that.
Worth including because the API is dead simple. If you just need to fire one message a day from a cron job, this is the overkill-free option.
Twilio's WhatsApp sandbox is free, but you have to ask testers to send a join <code> message first. Annoying for end users, fine for development.
Not useful for production unless you're paying, but the sandbox is a great way to test n8n flows before you commit.
If you're starting today and just want WhatsApp working in your n8n flow this weekend → Wappfly.
If you want to self-host and own everything → Evolution API.
If you need the Green Tick eventually → skip the indie tools and go straight to WhatsApp Cloud API.
If you're a "I'd rather write the code myself" type → Baileys or WPPConnect.
Everything else on this list is a specialty pick — useful, but not where I'd start.
If you're using anything that runs on WhatsApp Web (Wappfly's unofficial mode, Evolution, Baileys, Green API, UltraMsg) — don't blast 500 cold messages on day one from a fresh number. WhatsApp's spam detection is aggressive. Warm up the number, send to people who opted in, and you'll be fine.
If you're sending cold outbound at scale, you need the official Cloud API. Anything else and you'll be back here in two weeks asking why your number got banned.
That's the list. Build something good.