Telegram
Link your account to the Zuse Bifrost bot with a one-time code, receive alerts in a private chat, and ask the bot who you are linked as.
By the end of this page you will know how to link your account to the Zuse Bifrost bot, what arrives in the chat once you have, which commands the bot answers, and how to unlink.
Zuse Bifrost runs one Telegram bot for the whole workspace. A person links their own account to it with a one-time code; from then on the alert classes they route to Telegram arrive in that private chat, rendered from the same text the email carries, with a button that opens the page the alert is about.
Before you begin
| You need | Why |
|---|---|
| The bot set up for the workspace | Your administrator configures it. Until then the Telegram card says the bot is not set up. |
| Telegram on a device you hold | The code is redeemed from the chat you send it in, and that chat becomes your linked chat. |
Link your account
- Open Account Settings → Notifications. The Telegram card is at the top.
- Press Link Telegram. A six-character code appears, with how long it stays valid.
- Either press Open the bot, which opens Telegram with the code already in the start message, or open the bot yourself and send
/startfollowed by the code. - The bot answers that the chat is linked to your name. Back on the settings page, press I have sent it (or reload) and the card shows Linked.
A code works once and expires after a few minutes; Get a new code replaces it. If the chat you send the code from is already linked to another account, it moves to yours.
Linking is per person, in a private chat with the bot. The bot ignores group chats; project groups that should receive incident and release notices are addressed from the project's settings when those pages land.
What arrives in the chat
Every class of alert you route to Telegram in the alert destinations grid. A person who has not touched the grid is on the default, which sends every class to the linked chat; the critical classes (incidents, security, AI budget) are mailed as well, whatever the grid says.
A message carries the alert's title in bold, its lines, and one button that opens the page the alert points at. Text is escaped before it reaches Telegram, so a project called Payments <v2> reads as typed.
Commands
| Command | What it does |
|---|---|
/start CODE | Links the chat to the account that minted the code. |
/start | Says how to get a code, or that the chat is already linked. |
/me | Says which account the chat is linked as. |
/unlink | Detaches the chat. Alerts stop at once; link again any time with a fresh code. |
| anything else | The short help. |
More commands join as the phases land: your open work, the approvals waiting on you, and a quiet-hours switch.
Unlink
- In the chat, send
/unlink; or on Account Settings → Notifications, press Unlink on the Telegram card and confirm. - The chat's column disappears from the alert destinations grid, and alerts fall back on your other destinations.
All the fields
What happens next
- Linking with a grid you already shaped adds the chat to it carrying every class; a person still on the default needs no row, because the default already reaches the chat.
- Unlinking removes the chat's row from the grid, so nothing keeps pointing at a chat the bot may no longer reach.
- Nothing is announced to webhooks; linking is a personal setting.
Permissions
| Action | Who may do it |
|---|---|
| Link or unlink | You, on your own account |
Frequently asked
Related
- Notifications: the Notifications Center and the alert destinations grid.
- Profile: the email address that stays the safety net.
How is this guide?
Last updated on