Hi there. So I showed this to a dev friend of mine, and he told me that I shouldn't use it because I might get blocked by WhatsApp. Have you faced any issues like this? Apparently it is against their terms of service.
WhatsApp bot developer & business automation expert. Building custom bots and workflows with n8n, Make, and WhatsApp API (official & WAHA). 50+ happy clients.
Work
Founder at Achiya Automation — WhatsApp bots & business automation
Hey @mrdiin, great question — your friend is partly right, and I'll be straight with you about the tradeoffs.
The honest answer: WAHA uses the unofficial WhatsApp Web protocol (not WhatsApp's Business API), which does violate their TOS on paper. So the risk is real. But "real" doesn't mean "automatic ban." It depends entirely on how you use it.
What actually gets accounts banned, based on 50+ deployments I've watched:
Mass cold messaging to people who never contacted you first
Broadcasts that look promotional (dozens of unsaved numbers, sequential sends)
A fresh number with no history that suddenly sends hundreds of messages
Virtual / VoIP numbers — those are heavily flagged
What stays mostly safe in practice:
Replying to customers who messaged you first (auto-reply, support bots, ticketing) — which is exactly what this article's stack does
Conversational flows triggered by user input, not outbound prospecting
A real phone number with normal usage history
Sane rate limits (not 1000 messages/min)
For an inbound customer-support stack like this one, where customers start the conversation, ban risk is genuinely low across the deployments I've seen. WhatsApp can't reliably distinguish your auto-reply from a fast human typist on a real device.
If you need outbound or promotional messaging at any scale, switch to the official WhatsApp Business API (Meta direct, or providers like 360Dialog, Twilio, Infobip). More cost and more hoops, but it's sanctioned and survivable.
Not legal advice — engineering reality. Match the tool to the actual use case.
Lovely! Thanks for the response, will definitely keep that in mind. I've already spun up the stack and poked around with it using my personal number. Works like a charm. But yea, thank you for the breakdown. I also read the other post about your 50+ deployments and what you found to be safe limits. Thanks for this! Have a good day.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi there. So I showed this to a dev friend of mine, and he told me that I shouldn't use it because I might get blocked by WhatsApp. Have you faced any issues like this? Apparently it is against their terms of service.
Hey @mrdiin, great question — your friend is partly right, and I'll be straight with you about the tradeoffs.
The honest answer: WAHA uses the unofficial WhatsApp Web protocol (not WhatsApp's Business API), which does violate their TOS on paper. So the risk is real. But "real" doesn't mean "automatic ban." It depends entirely on how you use it.
What actually gets accounts banned, based on 50+ deployments I've watched:
What stays mostly safe in practice:
For an inbound customer-support stack like this one, where customers start the conversation, ban risk is genuinely low across the deployments I've seen. WhatsApp can't reliably distinguish your auto-reply from a fast human typist on a real device.
If you need outbound or promotional messaging at any scale, switch to the official WhatsApp Business API (Meta direct, or providers like 360Dialog, Twilio, Infobip). More cost and more hoops, but it's sanctioned and survivable.
Not legal advice — engineering reality. Match the tool to the actual use case.
Lovely! Thanks for the response, will definitely keep that in mind. I've already spun up the stack and poked around with it using my personal number. Works like a charm. But yea, thank you for the breakdown. I also read the other post about your 50+ deployments and what you found to be safe limits. Thanks for this! Have a good day.