Beyond the Telegram bot for alerts

July 23, 2026 · 3 min read

Almost every DevOps tutorial ends with “create a Telegram bot”. It works and it's free – but it also means your production alarm arrives as a chat message between holiday photos and group chats.

What the Telegram route really costs

Talk to BotFather, create a bot, store the token.
Find your chat ID (the classic stumbling block – start the chat, then read getUpdates).
Build the send URL: api.telegram.org/bot<TOKEN>/sendMessage?chat_id=…&text=…

And the daily reality: the alert lands in your normal Telegram notifications, with Telegram's sound, in the same list as every other chat. A failing payment webhook sounds exactly like a friend's message.

Where a service can't follow

Stripe, Shopify or Grafana can't build Telegram's URL format with token and chat ID – you'd need middleware. A Webhooky endpoint accepts arbitrary JSON directly, which is why third-party webhooks work without glue code.

« Telegram »
curl "https://api.telegram.org/bot/sendMessage?chat_id=&text=Backup%20done"

« Webhooky »
curl -X POST https://api.webhooky.app/YOUR_KEY \
  -d '{"title":"✅ Backup done","sound":"level_up_2"}'

When Telegram stays right

If the message belongs to a group – a team channel, notifications several people should discuss – Telegram is the better home. For alerts meant for you personally, a dedicated endpoint wins on two counts: its own sound per event type (an alarm you recognise without looking) and a history that only contains events, not conversations. See also: all notification tools compared.

Get Webhooky

Free for your first 100 notifications – set up your endpoint in two minutes.