Telegram alert channel
Telegram is a native alert channel in PulseStack. Connect a bot with a token and a chat id, and every monitor failure lands in the chat you already watch. It fires on recovery too, after a threshold you control.
No card for the Free plan. 14-day trial on paid plans. One of eight native alert channels.
PulseStack Bot
bot
Monitor DOWN
Checkout API
09:41
Monitor UP
Checkout API
09:47
8
native alert channels
8
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.
Message your new bot, or add it to the group or channel you want to alert. Then read the chat id, the unique number Telegram uses to address that conversation.
In your dashboard, add a Telegram alert channel and paste in the bot token and chat id. Give it a label like on-call or infra so you can tell channels apart later.
Choose which monitors deliver to this Telegram chat, set your consecutive-failure threshold, and send a test message. The moment a monitor fails, the alert lands in Telegram.
Every alert is a compact, readable message. Enough detail to triage from your phone, nothing to scroll past.
Monitor name
The friendly name you gave the check, so you know instantly what broke.
Status
DOWN on failure, or UP again on recovery, spelled out at a glance.
Monitor type
HTTP, Keyword, TCP Ping, Port, API, Heartbeat, DNS or Domain Expiry.
Target
The URL, host or endpoint being checked.
Reason
What the check saw: a timeout, a bad status code, a missing keyword.
Check location
Which monitoring location observed the failure.
Timestamp
When the state change happened, so you can line it up with your logs.
Duration
On recovery, how long the incident lasted before it cleared.
PulseStack sends each alert as a single call to Telegram's sendMessage method, addressed to your chat id and authenticated with your bot token. 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",
"parse_mode": "HTML",
"text": "<b>Monitor DOWN</b>\nCheckout API\nType: API\nReason: HTTP 503\nLocation: London\n09:41"
}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 and voice are an add-on available on the Team and Enterprise plans.
Whatever you watch, Telegram can carry the alert. Every monitor type below can deliver to your chat.
Watch a URL for downtime, slow responses and wrong status codes.
Confirm a word is present, or absent, in the page body.
Check a host answers at the network level.
Verify a specific port is open and accepting connections.
Probe a JSON endpoint and validate the response.
Expect a regular ping from a cron or background job.
Detect changed or missing DNS records.
Get warned before a domain lapses.
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 UP 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. Public status pages and maintenance windows keep the noise down further.
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, find the chat id for the chat you want alerts in, then add both as a Telegram contact in PulseStack. Assign that contact to any monitor and alerts start flowing.
Yes. Add your bot to a group or channel and use that chat's id when you set up the Telegram contact. Personal chats, groups and channels all work as delivery targets.
Alerts fire on failure and again on recovery, only after a configurable consecutive-failure threshold. That keeps the chat free of noise from brief blips.
Any of the six core monitor types - HTTP, Keyword, TCP Ping, Port, API and Heartbeat - plus DNS and Domain Expiry monitors can send their alerts to a Telegram contact.
You can start on the Free plan with 5 monitors and no card required, or take a 14-day trial on any paid plan to unlock all monitor types and faster check intervals down to 30 seconds on 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.