Alertes et notifications
Telegram alerts with a bot
Create a Telegram bot with BotFather, find your chat ID and receive FastPing alerts in a private chat, group or channel.
- In Telegram, open a chat with
@BotFatherand send/newbot. - Choose a display name and a username ending in
bot. - BotFather replies with a token such as
123456789:AAH…. Keep it secret: it controls the bot.
Use a dedicated bot for FastPing rather than one that other software also uses.
- Start the conversation the alerts should go to: open a private chat with your bot and send
/start, or add the bot to a group, or add it to a channel as an administrator allowed to post messages. - Send a message in that chat. In a group, send a command addressed to the bot, such as
/start@your_bot, so the bot receives it. - Open
https:/in your browser, with your token in place of/ api.telegram.org/ bot<token>/ getUpdates <token>, and find"chat":{"id":…}in the response.
Private chats have positive IDs. Groups and channels have negative IDs; supergroups and channels start with -100. For a public channel you can enter its username instead, such as @example_status.
In the dashboard, open Alert channels, choose the type Telegram, enter the chat ID (or @channelname) and the bot token, click Add channel and then Send test. Alerts arrive as plain messages: the headline (for example Down: Shop), the check's message and a link to the monitor.
| Message | What it means | What to do |
|---|---|---|
That destination does not look valid for this channel type. | The chat ID is not a number or an @username. | Copy the ID again from getUpdates, including a leading minus sign. |
Enter the bot token that @BotFather gave you: digits, a colon, then letters and numbers. | The token is not in the form 123456789:ABC…. | Copy it again from BotFather; do not include the word "bot" before the token. |
Test failed: Telegram HTTP 400 | Telegram rejected the message, usually because the chat ID is wrong or the bot is not a member of the chat. | Check the ID with getUpdates and add the bot to the group or channel. |
Test failed: Telegram HTTP 401 | The bot token is wrong or was revoked. | Get the current token from BotFather (/token). |
Test failed: Telegram HTTP 403 | The bot cannot write to the chat: it was removed, blocked, or is not an administrator of the channel. | Add the bot again, unblock it, or give it permission to post. |