A monitoring dashboard you must remember to open will fail you. A Telegram message that lands on your phone within minutes of a failure will not. Here is the full setup.
Of all the notification channels Uptime Kuma supports, Telegram is the one most small offices end up loving: it is free, instant, works on every phone, and needs no mail server. The setup has three parts — create a bot, learn your chat ID, connect both inside Uptime Kuma — and one habit that separates working systems from wishful ones: testing the alert on purpose, before a real outage does it for you.
👆 Illustrative example wording. The pair matters: the Down message wakes you up, the Up message lets you go back to sleep.
/newbot and follow the two questions: a display name, then a username that must end in botTreat the token like the key to your office. Never share a screenshot that shows it, never post it in a group, and if it ever leaks, return to BotFather and revoke it — a leaked token lets anyone send messages pretending to be your monitoring system.
Telegram bots cannot guess who to message; Kuma needs your numeric chat ID. The reliable way:
/start — a bot cannot message you before you have spoken to ithttps://api.telegram.org/botYOUR_TOKEN/getUpdates, replacing YOUR_TOKEN with your own token (this is a placeholder pattern, never a real token — keep yours private)"chat":{"id":... — that number is your chat IDFor a team, use a group instead: create a Telegram group, add the bot to it, send a message in the group, and read the group chat ID the same way (group IDs are negative numbers). Now one alert reaches the whole support team at once.
Support Team TelegramAlert quality is mostly monitor naming. “Server down” forces a phone call; “Branch Office - FileServer - Ping DOWN” is already half the diagnosis. Make sure the recovery message reaches you too — Uptime Kuma sends an Up notification when a monitor recovers, and that second message is what tells you a problem fixed itself (or a colleague fixed it) while you were driving to the office. Finally, keep total alert volume sane: attach phone alerts to devices that matter, and let trivia go to a quieter channel or nowhere.
Before declaring victory, run one honest drill: stop something real — unplug a test device, pause a service, or block a port — and wait. The Down alert should land on your phone within a few minutes (interval plus retries). Restore it and confirm the Up alert follows. Do this on day one, in daylight, while you are watching. The first real outage at night is the worst possible time to discover a mistyped chat ID.
Watch the video for the complete Uptime Kuma setup — notifications are configured on screen along with the monitors they protect.
▶️ Watch Full VideoThe usual causes, in order: you never sent the bot a first message (bots cannot start the conversation), the chat ID has a typo or is missing its minus sign for groups, or the notification was saved but never attached to any monitor. Use the Test button in the notification settings — it isolates the problem in seconds.
Yes, completely. Anyone holding the token controls the bot and can read and send its messages. Keep it out of screenshots, videos and shared documents. If it leaks, BotFather can revoke it and issue a new one — then update the token inside Uptime Kuma.
Yes — the cleanest way is one Telegram group containing the whole team, with the bot added and its group chat ID used in Uptime Kuma. Alternatively, create separate notification entries per person. Groups win in practice because the whole team sees the same Down and Up messages and nobody duplicates the rescue trip.