Original Summary

If you have ever tried automating WhatsApp for internal alerts, lead follow-ups, or workflow triggers, you know the friction with the official Meta Cloud API. You need a verified business account, you have to submit template messages for approval in advance, and you get billed per outbound conversation outside a 24-hour window. The standard workaround is self-hosting Baileys or WPPConnect in Docker. But that has its own annoying failure modes: sessions drop on container restarts, and rotating datacenter IPs trigger quick soft bans from WhatsApp. I built Supergreen ( https://supergreen.cc ) to handle the infrastructure part. Each account runs in its own isolated Docker container pinned to a static residential proxy to keep sessions alive across redeploys. Last week n8n verified our community node (n8n-nodes-supergreen) on n8n Cloud, so you can drag it onto the canvas without installing npm packages manually. What it supports: - Sending plain text, rich link previews, quoted replies, and typing indicators - Binary media (sending PDF documents, images, and audio directly from preceding workflow nodes) - Incoming message webhooks with a toggle to filter out the bot's own replies - WhatsApp group management and message handling - Telegram accounts under the same API The node code and ready-to-import n8n workflows are open source: https://github.com/uriva/n8n-nodes-supergreen Curious what messaging actions or triggers would be most useful to add next.   submitted by   /u/uriwa [link]   [comments]

  • 情报分类：服务器与云资源
  • 分类依据：内容涉及服务器、云资源或网络线路
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/14 11:05:02