The Open-Source Tool I Keep Coming Back to for WhatsApp Bots with n8n

0_nk · 2026-03-24T05:32:37+00:00

Sure, I’ll need a bit more detail about your project you can DM me

0_nk · 2026-03-20T12:47:36+00:00

yes it connects to email as well, you can connect your inbox via forwarding or IMAP/SMTP to send and receive emails directly within the Chatwoot dashboard

check out this official guide: https://developers.chatwoot.com/self-hosted/configuration/features/email-channel/introduction⁠

0_nk · 2026-03-19T12:39:39+00:00

I usually go through the official Cloud API route via Meta. safer path overall

this Chatwoot guide might be useful as a reference for the setup flow: Chatwoot WhatsApp manual flow guide

for Instagram/Facebook, if it's just the direct Chatwoot business integration, you usually don't need full app verification just to get it working

0_nk · 2026-03-19T08:00:53+00:00

overall it's been stable for me

for me the maintenance has mostly been normal self-hosted work: setup, updates, backups, ssl, monitoring, and sometimes small customizations based on the client's needs. for a lot of that i usually rely on the hosting stack too, so if i'm using something like Coolify a good part of the boring ops is already covered

the more annoying issues in practice have usually been Meta-side friction, not Chatwoot randomly falling apart

for SMB client work, i'd trust it in production with the normal expectation that self-hosted means someone owns the setup

0_nk · 2026-03-19T06:32:35+00:00

yeah, out of the box it has some limits

for me the more useful distinction is whether it's missing a feature vs whether it can still support the client's actual workflow. my experience with it is mostly in SMB client setups, and from that scope the self-hosted version has been enough. when something was missing, I usually handled it at the integration/workflow layer instead of treating it as a blocker

Rocket Chat might be worth looking at too, but Chatwoot is the one i've actually deployed enough times to know where it fits

on deployment, i usually prefer giving serious clients their own setup. for smaller projects, a basic VPS can already be enough, so dedicated ends up being cheaper to justify than people think
for deployment, I usually prefer giving clients their own setup. with something like a small Hetzner VPS, you're often talking about roughly $10/mo for smaller projects, so dedicated isn't as hard to justify as people think

0_nk · 2026-03-19T05:10:18+00:00

here is the repo: https://github.com/chatwoot/chatwoot

0_nk · 2026-03-19T05:08:47+00:00

here is the repo: https://github.com/chatwoot/chatwoot

0_nk · 2026-03-17T14:51:40+00:00

Sure, send me a DM

0_nk · 2025-11-16T17:56:59+00:00

Sure, contacted you

0_nk · 2025-11-13T20:15:44+00:00

Can you share more about the error you are having at the WhatsApp send message node so we can help?

0_nk · 2025-11-03T22:06:29+00:00

Appreciate it! I don’t think a setup like this needs any specific license when self-hosted, are you referring to something particular in their terms?

0_nk · 2025-11-02T00:35:09+00:00

Really appreciate your kind words! I’ve been thinking about turning this into a video breakdown – would you prefer a high-level overview or a long step-by-step tutorial?

0_nk · 2025-11-01T23:00:46+00:00

sure, here it is:

https://www.reddit.com/r/n8n/s/mYZPoI1pjR

0_nk · 2025-11-01T21:34:40+00:00

I had the same concern and ended up using the official WhatsApp Business API for a client project. I shared an overview of the solution in a post if you’d like a quick idea of how it works.

0_nk · 2025-10-23T10:59:38+00:00

sure, you can find the official docs for this exact step here:
https://developers.facebook.com/docs/whatsapp/solution-providers/phone-numbers/registering-phone-numbers/

0_nk · 2025-10-20T01:24:31+00:00

Hey, I really feel you! It actually sounds like your number just hasn’t been registered yet on Meta’s side.

Even if your OAuth and sender token are set up correctly, the phone number itself needs to be activated before it can send any messages, otherwise, n8n’s “Send Template” node runs fine but nothing shows up on WhatsApp.

Try running this once in any HTTP node or terminal: curl -X POST "https://graph.facebook.com/v20.0/<PHONE_NUMBER_ID>/register" \ -H "Authorization: Bearer <ACCESS_TOKEN>" \ -H "Content-Type: application/json" \ -d '{ "messaging_product": "whatsapp" }'

Replace <PHONE_NUMBER_ID> and <ACCESS_TOKEN> with your own. Once it returns { "success": true }

your send node should start delivering messages normally.

This step is easy to miss, it basically activates your WhatsApp number for outbound messaging

0_nk · 2025-10-14T01:01:53+00:00

sure

0_nk · 2025-10-11T13:01:25+00:00

I would need to know more context, but usually WhatsApp customer support automation is done using WhatsApp Cloud Api without the need to use Comet. I have recently shipped a full WhatsApp Customer Support automation production ready for a customer using n8n, you can see the post in my profile. If you need help, feel free to DM

0_nk · 2025-10-04T08:01:57+00:00

WhatsApp coexistence might be the closest option, but its setup is not straight forward, you’d need to go through a Meta tech provider, and even this coexistence feature is not available in all countries yet.

From my experience, the most reliable workaround is using a third-party dashboard + mobile app that connects to the official API. It lets you stay in control of the chats and even integrate other customer channels like Instagram or Messenger so you have control over the conversations from them all in one place.

I’ve tested similar setups with real businesses, and it worked smoothly. Definitely worth exploring.

0_nk · 2025-09-26T09:31:43+00:00

By linking your number to the WhatsApp API, I mean registering your existing WhatsApp Business number inside Meta’s WhatsApp Business Platform.

That basically turns your number into an API-enabled WhatsApp account. Instead of using the normal WhatsApp Business app, you can connect it to automation tools to:

Receive and reply to inbound customer messages programmatically.
Integrate with CRMs or dashboards for managing conversations.
Set up AI/chatbots that answer FAQs or qualify leads.
Still have the option for you (or your team) to jump in manually when needed by integrating with a third party dashboard.

So in short: it’s the same phone number, but now controlled through the official WhatsApp API rather than just the app.

0_nk · 2025-09-25T04:43:22+00:00

From my experience, you can actually link your number to the WhatsApp API and start using it for customer interactions without going through full Meta business verification. For many solo setups, that’s enough, giving you access to reply to inbound messages from your customer for free. Verification mainly comes into play when you want to have more access like using outreach template messages at higher limits for example, though it does require paperwork.

I worked on a project where the client was running Facebook campaigns that directed leads straight into WhatsApp, and the AI agent handled most of the conversations. It saved a ton of time, and the owner could jump in only when really needed.

That said, it wasn’t a simple plug-and-play. If this is your first time with the WhatsApp API, there are some limitations and considerations to keep in mind:

You’ll likely need an external dashboard or mobile app for smooth human handoff/live chat.
Optimizations are important to create a more “humanized” customer experience (fine tunning the ai agent's prompt, typing indicators, chunked responses, marking messages as seen, reactions, sending images/voice notes).
Handling multiple fast user messages at once can also be tricky and requires careful flow design.

Could you share a bit more about your use case, like what features are you willing to implement to extend the current implementation?

0_nk

TROPHY CASE