I’ve been building a Telegram bot called Repta—it helps small vendors generate receipts, log expenses, and generally run their business via chat. While working on it, I ran into a surprisingly annoying problem: broadcasting messages to my bot subscribers.
Most solutions I found were either built specifically for webhook setups (which doesn’t play well if your bot uses polling, like mine does) or they send messages on your bot’s behalf using their own infrastructure—not ideal if you want to keep things simple and branded.
So I ended up building a minimal broadcast tool that sends messages through your own Telegram bot. No webhook conflicts, no weird proxies. Just paste your bot token, enter your chat IDs, compose your message (media and scheduling supported- all local), and send.
If you’ve ran into the same pain point, I’d love to hear your thoughts.
Free access here: https://sweetcher.vercel.app
0 comments
—
How I stumbled upon building a broadcast tool · HackerTrans
Most solutions I found were either built specifically for webhook setups (which doesn’t play well if your bot uses polling, like mine does) or they send messages on your bot’s behalf using their own infrastructure—not ideal if you want to keep things simple and branded.
So I ended up building a minimal broadcast tool that sends messages through your own Telegram bot. No webhook conflicts, no weird proxies. Just paste your bot token, enter your chat IDs, compose your message (media and scheduling supported- all local), and send.
If you’ve ran into the same pain point, I’d love to hear your thoughts. Free access here: https://sweetcher.vercel.app