Telegram alert channel
Telegram is a native alert channel in PulseStack. Connect a bot with a token and a chat id, and every confirmed monitor failure lands in the chat you already watch. It fires on recovery too.
No card for the Free plan or the 14-day free trial on paid plans. One of eight native alert channels.
PulseStack Bot
bot
🔴 Monitor DOWN
Locations:
Time: 2026-07-25T08:41:07.000Z
09:41
🟢 Monitor RECOVERED
09:47
Example. The recovery message also lists Type, Locations and Time. Alerts come from the bot you create, under the name you give it.
8
native alert channels
9
monitor types supported
2
fields to connect: token + chat id
Up + Down
alerts on failure and recovery
Email gets buried. A dashboard only helps when someone is looking at it. Telegram sits on the home screen, rings on the lock screen and syncs across every device your on-call engineer owns. That is exactly where a downtime alert should arrive.
Because PulseStack talks to the official Telegram Bot API directly, there is no third-party relay to sign up for and nothing to keep patched. A bot token and a chat id are all the plumbing you need.
From zero to a live alert in a few minutes. No plugins, no OAuth dance, just a token and a chat id.
Open a chat with @BotFather in Telegram, send /newbot and follow the prompts. BotFather hands you a bot token, a long string that authenticates your bot with the Bot API.
Send your new bot a message first (bots cannot start a chat), or add it to the group, or make it an administrator of the channel. @userinfobot replies with your own ID for a personal chat; group IDs are negative, and supergroup and channel IDs start with -100.
Open Alert Contacts, click Add contact, choose Telegram and fill in Bot token and Chat ID. Give it a label like on-call or infra so you can tell contacts apart later; the token is hidden in the list once saved.
Click Send test, then tick the contact under Notify on failure on each monitor that should message this chat. Once a failure is confirmed, the alert lands in Telegram.
Every alert is a compact, readable message. Enough detail to triage from your phone, nothing to scroll past.
Title
🔴 Monitor DOWN or 🟢 Monitor RECOVERED, in bold.
Monitor
The name you gave the check, or its URL if it has no name. The URL is not otherwise included.
Type
HTTP, KEYWORD, TCP_PING, PORT, API, HEARTBEAT, SSL, DNS or DOMAIN_EXPIRY.
Error
What failed. For multi-location monitors, how many locations failed; for SSL, DNS, domain expiry and heartbeat monitors, the check's own message.
Locations
Each city with ✅ or ❌ and its response time, for HTTP, keyword, API, ping and port monitors.
Time
When the alert was sent, in UTC (ISO 8601), so you can line it up with your logs.
Recovery
Status: Back online, with how long the monitor was down.
PulseStack sends each alert as a single call to Telegram's sendMessage method, addressed to your chat id, authenticated with your bot token and formatted with Telegram's HTML mode. The monitor name and error text are escaped, so a name such as api_prod or [eu]*web* arrives exactly as written. That is the whole integration. No queues to babysit, no webhook receiver to host.
Prefer to shape the payload yourself, or forward it into a tool Telegram does not cover natively? Use the Webhook channel instead and you get the raw JSON to route anywhere.
POST https://api.telegram.org/bot<token>/sendMessage
{
"chat_id": "-1001234567890",
"text": "🔴 <b>Monitor DOWN</b>\n\n<b>Monitor:</b> Checkout API\n<b>Type:</b> API\nError: Down from 2/3 locations: London, New York\n\n<b>Locations:</b>\n❌ London (412ms)\n❌ New York (388ms)\n✅ Sydney (291ms)\n<b>Time:</b> 2026-07-25T08:41:07.000Z",
"parse_mode": "HTML"
}Telegram is one of eight channels PulseStack talks to directly. Mix and match them per monitor. Tools like Zapier and Google Chat are not native but connect through the Webhook channel.
SMS alerts are included on the Team and Enterprise plans. See all integrations.
Whatever you watch, Telegram can carry the alert. All nine monitor types below can deliver to your chat.
Watch a URL for downtime and wrong status codes, with response times charted.
Confirm a word is present, or absent, in the page body.
Check a host accepts TCP connections, with connection time.
Verify a specific port is open and accepting connections.
Send a request with your method, headers and body, and check the status code.
Expect a regular ping from a cron or background job.
A message a set number of days before expiry (7 by default), or when the certificate is not trusted.
A message when no record of the chosen type holds the value you expect.
A message a set number of days before the registration runs out (7 by default).
You already live in Telegram. A single bot messages your personal chat the moment your side project stops responding, no extra app, no per-seat cost.
Point a shared group chat at your production monitors. Everyone on the rota sees the same DOWN and RECOVERED messages, so the fastest responder can jump straight in.
Give each client their own Telegram channel with its own bot token and chat id, then route just that client's monitors there. Clean separation, no crossed wires.
Telegram travels well across regions and mobile networks. Multi-location checks confirm a real outage before your distributed team is pinged.
The message only matters because the monitoring behind it is honest. PulseStack checks from multiple locations and confirms a failure before it ever reaches your chat, so a DOWN in Telegram means something is genuinely wrong.
Start with Send test next to the contact on the Alert Contacts page. It sends a fixed test message through your bot straight away, and if Telegram refuses it the error shows the status code, for example Telegram returned 403.
Copy the whole token from @BotFather again (it looks like 123456:ABC...) and replace the contact. A token you revoked or regenerated in BotFather stops working straight away.
Telegram answers chat not found for an ID it cannot match. Group IDs are negative, and supergroup and channel IDs start with -100. If a group was upgraded to a supergroup, its ID changed to a -100 one.
A bot cannot message a person who has not started a chat with it or who blocked it, a group it was removed from, or a channel where it is not an administrator. Send the bot /start, add it back, or make it a channel admin.
Alerts go to the contacts ticked under Notify on failure (every contact if none are ticked), and only when a monitor goes down or recovers, once each with no retry. If an alert looks wrong, see why a monitor status can be wrong.
Yes. Telegram is one of eight native alert channels, alongside Email, SMS, Slack, Microsoft Teams, Discord, PagerDuty and Webhooks. It uses the official Telegram Bot API to deliver messages.
Create a bot with @BotFather to get a bot token, send the bot a message (or add it to your group or channel) and find the chat ID. In PulseStack™, open Alert Contacts, click Add contact, choose Telegram, enter the bot token and chat ID, and click Send test. Then tick the contact under Notify on failure on your monitors.
Yes. Add the bot to the group, or make it an administrator of the channel, and use that chat's ID. Group IDs are negative numbers, and supergroup and channel IDs start with -100. Personal chats, groups and channels all work as delivery targets.
Alerts fire on failure and again on recovery. Every failure is double-checked first, which keeps the chat free of noise from brief blips.
Any of the nine monitor types (HTTP, Keyword, TCP Ping, Port, API, Heartbeat, SSL certificate, DNS record and domain expiry) can send their alerts to a Telegram contact.
Yes. The Free plan includes 5 HTTP monitors with email alerts and no card required, so Telegram alerts need a paid plan. Every paid plan starts with a 14-day free trial with no card needed, and unlocks all monitor types with checks every 60 seconds on Starter and every 30 seconds on Pro, Team and Enterprise.
Wire up a bot in minutes and never miss a downtime message again. Start free, no card needed, and add Telegram the moment you are on a paid plan.