Send alerts to Telegram (bot token and chat ID)

Create a Telegram bot with @BotFather, find the chat ID with getUpdates (groups, supergroups, channels), then verify the chat with a code. Free on every plan.

Updated By the Uptime Tracker team
  1. Create a botIn Telegram, message @BotFather, send /newbot, pick a name and a username ending in "bot", and copy the token it sends.
  2. Give the bot access to the chatFor private alerts open the bot and press Start. For a group add the bot as a member; for a channel add it as an administrator that can post.
  3. Find the chat IDOpen https://api.telegram.org/bot<token>/getUpdates in a browser and copy the number after "chat":{"id":. Group and channel IDs are negative.
  4. Add the destinationIn Integrations → Add destination, choose "Use my own bot" on the Telegram card (or "Set up Telegram" where Connect Telegram is not offered), enter a Name, the Chat id or @channel and the Bot token, then "Add destination".
  5. Verify with the codeThe bot posts an 8-character code in the chat. Choose "Enter chat code", type the code and choose Verify within 1 hour.
  6. Send a testChoose "Send test" and check the chat.

Telegram alerts are available on every plan, including Free. The quickest way is to connect the Uptime Tracker bot: no token and no chat ID needed. If you prefer messages from a bot you control, use your own bot instead (sections 1–5 below); Uptime Tracker then verifies the chat with a code before any alert is sent.

Before you start

  • Any Uptime Tracker plan, and the owner, admin or operator role.
  • The Telegram app, and a browser for one lookup step.
  • Decide where alerts should go: a private chat with you, a group, or a channel.

Quickest: connect with the Uptime Tracker bot

  1. In Integrations → Add destination, find Telegram and choose Connect Telegram. The connection wizard opens on Integrations → Destinations with a one-time code; it works once and expires after 30 minutes.
  2. Choose where alerts should go:
    • Add to a group opens Telegram and lets you pick the group. The bot joins and connects it.
    • Message the bot opens a private chat; press Start.
    • For a channel, add the bot as an administrator that can post, then post the /start <code> command shown on the page (there is a Copy button) in the channel.
  3. The bot posts a confirmation in the chat and the page updates by itself. The destination is verified straight away: the code from your signed-in session is the proof.
  4. Choose Send test.

If the group is later upgraded to a supergroup, the destination follows the new chat automatically. If someone removes or blocks the bot, the destination is disabled and your other destinations are told; connecting the same chat again re-enables it. Deleting the destination does not remove the bot from the chat.

Acknowledge from Telegram

Alerts sent by the Uptime Tracker bot have an Acknowledge button. The first time you press it, the bot sends you a private link (valid 15 minutes) to link your Telegram account to your Uptime Tracker sign-in; you can also send /link to the bot in a private chat. After that, pressing Acknowledge acknowledges the incident as you, with your role's permissions, and the message shows who acknowledged. Linked chat accounts can be unlinked on Integrations → Destinations.

Prefer your own bot? Follow the steps below.

1. Create a bot and copy its token

  1. In Telegram, open a chat with @BotFather (look for the blue verified tick).
  2. Send /newbot.
  3. Send a display name, for example "Acme Uptime".
  4. Send a username that ends in bot, for example acme_uptime_bot.
  5. BotFather replies with a token, shaped like 123456789:AAH4k…: digits, a colon, then about 35 letters, digits, - and _. Copy the whole token. Keep it secret; anyone with it controls the bot. If it leaks, send /revoke to BotFather for a new one.

2. Give the bot access to the chat

  • Private chat with you: search for your bot's username, open it and press Start. Bots cannot message anyone who has not started them.
  • Group: open the group, choose Add members and add the bot by its username. Then send a message that mentions it, such as /start@acme_uptime_bot.
  • Channel: open the channel's administrators, add the bot as an administrator and allow it to post messages. Then post anything in the channel.

Forum groups with topics: alerts are posted to the General topic.

3. Find the chat ID

Uptime Tracker needs the numeric chat ID (or, for a public channel only, its @channelname). The most reliable way to find it is Telegram's getUpdates method, which lists recent messages your bot has seen:

  1. Make sure something happened in the chat after the bot joined: you pressed Start, mentioned the bot in the group, or posted in the channel.
  2. Open this address in your browser, replacing YOUR_BOT_TOKEN with the token from step 1 (keep the word bot in front of it):
    https://api.telegram.org/botYOUR_BOT_TOKEN/getUpdates
  3. In the response, find the "chat" object for your chat and copy the number after "id":. For example:
    "chat":{"id":-1001234567890,"title":"Ops alerts","type":"supergroup"}

How to read the ID:

Chat type"type"ID looks like
Private chat with youprivatePositive, e.g. 123456789 (your user ID)
Basic groupgroupNegative, e.g. -987654321
SupergroupsupergroupNegative with a -100 prefix, e.g. -1001234567890
Channelchannel (inside "channel_post")Negative with a -100 prefix

Copy the ID exactly, including the minus sign and the full -100 prefix. A response of {"ok":true,"result":[]} means the bot has not seen a message yet: send another message (in groups, mention the bot), wait a few seconds and reload. Telegram only keeps updates for 24 hours. In a group, the update where the bot was added ("my_chat_member") also contains the chat ID.

For a public channel you can skip the lookup and enter its public name, such as @acme_status. This does not work for private chats, groups or user names.

4. Add the destination

  1. In Uptime Tracker, go to Integrations → Add destination, find Telegram and choose Use my own bot (or Set up Telegram where Connect Telegram is not offered).
  2. Enter a Name, shown in rules and the delivery log.
  3. Enter the Chat id or @channel, for example -1001234567890.
  4. Paste the Bot token. It is stored encrypted and never shown again.
  5. Tick Personal destination — only notify me when I am on call only if this is your private chat and should be used for on-call paging (Team).
  6. Choose Add destination.

5. Verify the chat with the code

Right after saving, the bot posts a message in the chat: "Confirm this chat for Uptime Tracker alerts. Enter this code in the destination settings: …" with an 8-character code. The destination shows pending until you enter it:

  1. On Integrations → Destinations, under Configured destinations, find the Telegram destination and choose Enter chat code.
  2. Type the code into Code from the Telegram chat. It uses capital letters and digits without look-alikes (no 0, O, 1, I or L); case does not matter.
  3. Choose Verify. The destination shows verified and alerts start.

The code is valid for 1 hour; after that the destination shows expired. Choose Resend code for a new one. After a code was delivered you can resend at most once every 10 minutes; if the code message could not be delivered, Resend code works again immediately. Only the newest code works. Until the chat is verified, only the code message is ever sent to it, so a mistyped chat ID cannot receive alerts.

If Telegram refuses the code message, the destination shows failed with Telegram's reason, for example "Telegram: chat not found". See troubleshooting below.

6. Send a test

Choose Send test. The bot posts "Test notification" in the chat. From now on you receive a message when a monitor goes down and when it recovers. Down alerts, reminders and escalation pages include a Reason: line, such as HTTP 503 Service Unavailable or Timed out after 10s.

Change the chat ID or bot token

Choose Edit connection on the destination, enter the new chat ID and/or the new bot token (leave a field empty to keep its current value) and choose Save connection. The values are checked like a new destination. Because the recipient changed, verification starts over: the bot posts a new code in the chat, and alerts resume once you enter it with Enter chat code. Saving also re-enables a destination that was disabled after delivery failures. You never need to delete and re-create the destination, so routing rules that use it keep working.

Troubleshooting

When Telegram gives a definitive answer, such as an unknown chat or a blocked bot, delivery stops at once with a clear reason instead of retrying. Where you see it depends on the destination:

  • Not verified yet: the destination shows failed with the reason in Configured destinations. Fix the cause, then choose Resend code (it works immediately after a failed code), or correct the chat ID or token with Edit connection, which sends a new code.
  • Already verified: the destination is disabled with the reason, and the workspace is told through its other destinations with a "Notification destination disabled" alert. Fix the cause, then choose Re-enable and Send test, or correct the details with Edit connection.

The reasons and what to do:

  • "Telegram: chat not found": the chat ID is wrong or incomplete (a supergroup or channel ID is missing its -100 prefix), or the bot was never added to the group or channel. Check the ID with getUpdates and correct it with Edit connection.
  • "Telegram: the bot cannot start a conversation": in a private chat, open the bot and press Start, then Resend code.
  • "Telegram: the bot was blocked by the user": unblock the bot in Telegram (and press Start again).
  • "Telegram: the bot was removed from the chat" or "the bot is not a member of the chat": add the bot back to the group, or as an administrator to the channel.
  • "Telegram: the bot needs administrator rights to post in this channel" or "the bot is not allowed to send messages in this chat": make the bot an administrator that can post messages, or allow members to send messages in the group.
  • "Telegram: the group was upgraded to a supergroup and has a new chat ID (-100…)": Telegram gave the group a new ID when it became a supergroup. Copy the new ID from the message into Edit connection.
  • "Telegram rejected the bot token (Unauthorized)" or "Telegram did not recognize the bot token (Not Found)": the token is wrong or was revoked with /revoke. Paste the current token from BotFather with Edit connection.
  • "Telegram destinations need a chat id (e.g. -1001234567890) or @channel name": the chat ID contains spaces or other characters, or the @name is shorter than 5 characters. Paste only the number, including the minus sign.
  • "The referenced secret is not a Telegram bot token (123456:ABC...)": the token is incomplete. Copy the whole token from BotFather, including the digits before the colon.
  • "The code is wrong or expired; resend it from the destination": the code is older than 1 hour or a newer one was sent. Use Resend code and enter the newest code.
  • "A verification message was sent in the last 10 minutes": the last code was delivered less than 10 minutes ago. Check the chat for it, or wait before resending.
  • getUpdates returns an error about a webhook: the bot already has a webhook set by another tool, which disables getUpdates. Create a separate bot for Uptime Tracker.

Temporary problems, such as Telegram's rate limit, are retried automatically. Every attempt is listed under Integrations → Deliveries: look for the event destination.verification (the code) or destination.test.

FAQ

Frequently asked questions

How do I find my Telegram chat ID?

Send a message in the chat (in groups, mention the bot), then open https://api.telegram.org/bot/getUpdates in a browser and copy the number after "chat":{"id":. Group IDs are negative, and supergroup and channel IDs start with -100.

Why does Telegram need a verification code?

The code proves the bot can post to that chat and that you control it, so alerts never go to a wrong or mistyped chat ID.

How long is the Telegram code valid?

1 hour. Use Resend code for a new one, at most once every 10 minutes after a delivered code, or immediately if the code could not be delivered.

Why does my Telegram destination say failed?

Telegram refused the code message, for example because the chat was not found or the bot was not started. The reason is shown on the destination. Fix it, then use Resend code, or correct the chat ID or token with Edit connection.

Can I change the chat ID or bot token later?

Yes. Use Edit connection on the destination. A new code is sent to the chat and alerts resume once you enter it.

Can I send alerts to a Telegram channel?

Yes. Add the bot as a channel administrator that can post messages, then use the channel's -100… ID or, for a public channel, its @name.

Is my bot token visible after saving?

No. The bot token is stored encrypted and never shown again.

Uptime Tracker

Start monitoring in under five minutes

Start on the free plan — commercial use allowed. No credit card required.

  • Free forever plan
  • No credit card
  • Cancel anytime