brily
Integrations

Telegram.

For teams that live on Telegram instead of Slack — especially common outside North America. Bot-based routing with the same severity and time-window controls, plus inline action buttons to ack or promote alerts.

Connect the bot

  1. In Brily, go to Settings → Integrations → Telegram.
  2. Click Install. You'll see a prompt to open t.me/BrilyAlertsBot — our verified bot.
  3. In Telegram, tap Start. The bot replies with a one-time code.
  4. Paste the code back into Brily. The connection is now tied to your Telegram account — not a server token you have to rotate.

After linking, the bot can deliver to three destination types: private chat with you, a group chat where the bot is a member, or a channel where the bot is an admin.

Add a destination

Private chat

Once connected, your personal chat is available immediately as a destination labelled dm:your-name. Good for on-call engineers who want P1 alerts directly on their phone.

Group chat

Add @BrilyAlertsBotto the group. Once it's a member, the group appears in Settings → Integrations → Telegram → Destinations with a grp:prefix. Pin the group in your Telegram client if it's a high-signal ops channel.

Channel

For broadcast-only delivery (one-way from Brily to a read-only audience), promote @BrilyAlertsBot to administrator in the channel with Post Messages permission. The channel appears with a chn: prefix.

Create an alert route

Alert routes work identically across all channels. Under Alerts → Routes → New route, pick:

  • Match criteria — severity, project, tag.
  • Destination — a Telegram target (dm:, grp:, or chn:).
  • Time window — always or a named business window.

Recommended layout for teams that Telegram-first:

  • P1 (outage) → on-call engineer's DM and team group · always
  • P2 (degradation) → team group · business hours
  • P3 (info) → broadcast channel · business hours

Alert formatting

Telegram posts are Markdown-formatted. A P1 looks like:

🔴 *P1 — api-health*
2 of 3 probes failing · 503 Service Unavailable for 3m 12s

Regions failing: fra, hel
Last error: status 503

[Open in Brily] [Promote to incident] [View runbook]

The three action buttons at the bottom are inline keyboard buttons. Open in Brily deep-links to the alert, Promote to incident opens the in-chat flow (Brily asks you which status page and severity, you tap one message to confirm), and View runbook opens the URL you attached to the monitor.

Promote to incident, from Telegram

Tap the inline button. The bot replies with a pre-filled draft: affected component, severity, proposed initial update. Tap Publish and your status page goes live with the incident — no need to leave Telegram.

The bot remembers the last status page you published to, per project, so repeat flows are a single tap after the first one.

Muting during maintenance

Create a maintenance window in Alerts → Maintenance windows. Alerts matching the window are suppressed across all channels including Telegram; the bot posts a single summary message when the window ends so you know what would have fired.

Common issues

"Bot was blocked by the user"

If you blocked the bot in Telegram, it can't deliver. Unblock@BrilyAlertsBot from your Telegram account and reconnect from the Brily dashboard.

Group messages not arriving

Telegram requires bots in groups to be explicitly pinged or granted "All messages" privacy. Our onboarding disables privacy mode on our end, but if you're using a newer BotFather profile, verify under Group privacy in Telegram.

Channel messages need admin status

Channels require the bot to be an administrator (not just a member) with Post Messagespermission. If delivery fails silently, check the channel's admin list.

Revoking access

In Brily: Settings → Integrations → Telegram → Disconnect. In Telegram: /stop in the DM with the bot revokes the token immediately. Do both to fully sever the connection.

Data handling

Telegram receives: the alert message body, severity, a deep link back to Brily, and an inline-button payload that identifies the alert ID. No customer-data beyond what you put into monitor names is sent. Telegram's data-handling practices are governed by their own privacy policy — consult your compliance team if Telegram is new in your stack.

Next
WhatsApp