I maintain n8n-nodes-wafly, a community node for a WhatsApp API, and I kept rebuilding the same five flows for different projects. I cleaned them up and I’m sharing the JSONs.
- Reply to grouped WhatsApp messages with an AI agent — buffers messages that arrive in a burst so the agent answers once instead of three times. This is the one that took me longest to get right.
- Qualify inbound WhatsApp leads with AI and hand hot ones to a human — the agent scores the conversation and hot leads get routed to a person.
- Approve join requests and remove link spam in WhatsApp groups — the instance number has to be a group admin.
- Send one-time passwords over WhatsApp with SMS fallback — validates the number first, falls back to SMS when WhatsApp is not reachable.
- Check the WhatsApp connection on a schedule and alert when the number drops — the failure mode nobody plans for until it happens in production.
JSONs: n8n-nodes-wafly/examples/templates at main · iagovelasco3/n8n-nodes-wafly · GitHub
Two honest caveats. This uses a community node, so it runs on self-hosted n8n only, not on Cloud. And the message-buffering logic in the AI agent template is the part I am least sure about, so tell me if you find a better way to handle it.
Happy to answer questions about any of them.