INTEGRATION

Telegram

Send an alert from a Telegram bot to a chat, group or channel.

How the wire-up works

Three things to know: the protocol, the credential, and what the alert payload looks like. The setup is the same on free and Pro.

Protocol
smtp-email
Credential
Bot token (from @BotFather) + Chat ID (numeric, or @channelname for a public channel). The bot must be added to the target chat.
Payload
sendMessage with Markdown-formatted text — title, monitor name, status, latency, and a link to the endpoint. Telegram strips the unsupported HTML tags.

What it supports

The grid below describes what the channel itself supports once wired up. All channels are available on the free plan unless the badge says otherwise.

Free planSupportedNo card, no expiry.
Pro planSupportedSame on free and Pro.
InteractiveNot supportedOne-way push only.
Incoming mentionsNot supportedOutbound-only.
Rich attachmentsNot supportedPlain text or simple message.
TLS in transitSupportedHTTPS / WSS — no plaintext fallback.

When Telegram is the right pick

Your team is on Telegram and you want the alerts to land where the team already is — a small dev group, a SRE on-call group, a public status channel.

Wire Telegram to ZnowPulse in two minutes.

Free plan. No card. Cancel any time.