Check on your server from your phone (secure remote panel)
A read-first web panel served over your own tunnel so you can see account health, queue depth and risk without walking back to the desktop. The cockpit for your headless server.
Tell us what to build next and vote on what matters to you. When an idea you backed ships, we email you.
Ideas are reviewed before appearing on the board.
A read-first web panel served over your own tunnel so you can see account health, queue depth and risk without walking back to the desktop. The cockpit for your headless server.
A small visual builder for the common flows — auto-reply, drip, keyword routing — for people who don't want to stand up n8n just to answer "hi" with a menu.
Let a Pro license cover a small team's phones by adding seats, instead of buying a whole new license per number.
Drop-in mini-tools inside the remote panel — a broadcast composer, a warm-up tracker, a contact cleaner — so the panel grows without waiting on a full app release.
When someone first messages me, I want to drip a short onboarding series — welcome now, a tip tomorrow, a check-in in three days — paced by the anti-ban engine.
Most e-commerce setups want the same thing: when an order is placed or shipped, send a WhatsApp confirmation. Ship a copy-paste recipe so people don't build it from zero.
When I add a second number for the same business, let me clone the warm-up plan instead of setting it all up again from scratch.
An out-of-office style responder I can turn on for specific chats, that stays quiet during my night window instead of firing at 2am.
"Phase 2 of 3, 340/500" means nothing at a glance. Give me red/amber/green plus "safe to send ~X more today" in plain language.
If my automation endpoint is offline for a few minutes I don't want to silently lose events. Retry with backoff, and give me a list of what failed so I can replay it.
After a broadcast I want a simple split: these contacts replied, these opened nothing back. Right now I'm guessing whether a campaign landed.
Sometimes you realise the template has a typo halfway through a batch. I want a hard pause that stops new sends immediately and lets me resume (or cancel the rest) without rebuilding the list.
One node that hands your LLM the recent conversation and a clean transcript, so an AI reply actually knows what was said instead of answering blind.
A fresh number blasting messages on day one is a dead number. Ramp new accounts gradually (0 → 500/day over a few days) so they build a normal-looking history first.
Getting your self-hosted server reachable from n8n Cloud or a webhook shouldn't mean port-forwarding. Download the tunnel binary, click connect, get a stable hostname.
Each connected number should present one consistent device fingerprint for its whole life — assigned once, never shuffled. Rotating identities is exactly what gets numbers flagged.
Instead of a blunt 24-hour lockout, back off automatically when the risk score climbs and lift the pause as it decays. Protect the number without babysitting it.
Set a nightly window per account where the server holds sends and drains the queue the next morning. Nothing feels more like a bot than a 3am "reminder".
For accounts that are properly warmed and behaving, let Pro users opt into much higher ceilings — up to 120/min and 5,000/day — behind a 72-hour warm-up and a clear acknowledgement.
Drop in a spreadsheet, map "phone" and "name" (and whatever custom fields), preview a few rows, import. The manual copy-paste is the worst part of getting started.