Telegram integration
Outage alerts your on-call group can act on, right in Telegram
Add the InfraNest bot to your team’s Telegram group and everyone sees a monitor go down at the same moment. Anyone on the team can acknowledge or silence it from the message, the message says who is on it, and it updates itself when the problem is over.
On every plan, one chat on Free · Nothing to copy · You pick the group in Telegram
- Acknowledge or silence from the alert, for the whole group
- Alerts that update themselves, readable at a glance
- Alerts in the topic you choose, the ongoing outage pinned
- Your own alerts and quick commands in a private chat
One incident, not several: the effects are grouped under the cause.
- 2:33 PMDeploy of northwyndr/storefront (f19e6c7)Deploys
- 2:36 PMCheckout flow failed: Checkout returning 503Monitoring
- 2:36 PMAPI health failed too, grouped under this incidentMonitoring
- 2:36 PMAlert sent to Ops team — email, On-call — critical only, Northwind on-callNotifications
Northwind on-call
group
InfraNest
🔴 Checkout flow is DOWN
14:36
Acknowledge from the message, and the whole group sees who has it
Each alert arrives with buttons the team can use. Acknowledge says you are on it: the message shows your name and the time for everybody, the repeat alerts stop, and nobody else chases it. Silence 1 h quiets the monitor for an hour while you work. Once someone is on it, Add a note asks for a few words for the team, or anyone can simply reply to the alert: the reply becomes a note on the incident, and never reaches your status page.
- Every tap acts as the person who made it, with their own role
- Works for everyone in the group who has linked their own Telegram
- Notes stay with your team, never on your status page
- Choose which alerts reach the group — see alert routing
Northwind on-call
group
InfraNest
🔴 Marketing site is DOWN
Acknowledged by Sam at 15:05
15:01
👀InfraNest
🔴 Marketing site is DOWN
📝 Sam, reply to this message with your note for the team on Marketing site. Only the team sees it, never the status page.
15:05
One message per outage, and you can read it at a glance
When the problem is over, InfraNest edits the alert to say so and how long it lasted, and posts the recovery as a reply to it, so a busy group never shows an outage as still going on. It also reacts to its own alerts: 👀 once somebody is on it, 👌 once it is over. Notes and public status updates written on the incident, in InfraNest or in another connected tool, arrive as replies to the alert too.
- “Resolved after …” on the alert itself
- 👀 means someone is on it, 👌 means it is over
- Notes and status updates follow the incident as replies
- Long error details folded into a short quote
Northwind on-call
group
InfraNest
✅ Resolved after 15 min
🔴 Marketing site is DOWN
15:01
👌InfraNest
🔴 Marketing site is DOWN
🟢 Marketing site is UP
15:16
Alerts in the right topic, and the ongoing outage pinned
In a group with topics, alerts go to the topic where you added InfraNest; send /here in another topic to move them there. Send /pin on and a critical alert is pinned while the problem is open and unpinned when it is over, so it does not scroll away in a busy group. Pinning needs InfraNest to be a group admin allowed to pin messages, and it tells you when it is not.
- /here in General moves the alerts back
- Unpinned by itself when the problem is over
- Set from the group by anyone linked and allowed to change monitoring
- When the group becomes a supergroup, InfraNest follows it
Northwind on-call
group
InfraNest
Done: this group’s alerts now arrive in this topic.
InfraNest
Done: a critical alert is pinned while the problem is open, and unpinned when it is over.
Your own alerts, and quick answers, in a private chat
Besides the team’s group, each person can link their own Telegram and get their own alerts there, with buttons that work only for them: acknowledge, silence, put off an expiring certificate for a week, approve a request. In that chat, /status shows what needs you right now, or how one monitor, domain or server is doing; /pause quiets your notifications for an hour, until tomorrow or for a week; /update posts a public status update after you have seen it; and /run starts one of your manual automations after a confirmation.
- Already in the group? Your own message about it arrives silently
- Quiet hours and do not disturb apply
- Hide the details on your lock screen until you open it
- Share how one thing is doing in any chat, from the message box
InfraNest
bot
What I understand
- /status — what needs you right now
- /update — post a public status update on an open incident
- /run — run one of your manual automations, after a confirmation
- /app — open the InfraNest app
- ↩️ Reply to an alert — a note for your team on it
- /pause — no notifications for an hour (or /pause tomorrow, /pause week)
- /back — notifications on again
- /start — link this Telegram to InfraNest
- /stop — unlink it from every workspace
- /help — this list
Send your alerts to your on-call group
On every plan, with one chat destination on Free. Pick the group in Telegram and the bot does the rest.
Connect Telegram in a few minutes
Choose Add a Telegram group, open the link (or scan the QR code on your phone) and pick your team’s group. The InfraNest bot joins it and says it is linked. Rather send from a bot of your own? That works too, but its alerts arrive without buttons.
- 1
Pick your team's group
Gets your whole team seeing alerts at the same moment — go to Integrations → Telegram, click Connect, and choose Add a Telegram group.
- 2
Let the bot join the group
Open Telegram on your computer or phone and confirm which group to add the InfraNest bot to.
- 3
Choose which alerts go there
Decide what the group actually sees — under Alerts, pick the Telegram group as a destination for the rules you want, like monitor down and recovered.
That’s it — Telegram is connected.
Full setup guideSet up with AI
I use Telegram, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: Bot token. Walk me through creating that in Telegram: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.
Often connected together
Questions about the Telegram integration
#Can everyone in the group use the Acknowledge and Silence buttons?
Anyone in the group who has linked their own Telegram to InfraNest and belongs to the workspace can use them. Each press acts as that person with their own permissions, and is checked again at the moment it's pressed.
#What happens if I remove the bot from the group?
The destination is removed along with it, so alerts stop arriving there. You can also turn the destination off or delete it from Integrations → Telegram or Alerts → Destinations without removing the bot.
#Can I change what alerts are sent, or does Telegram decide that?
You choose it on InfraNest's side: a group only receives the alert rules you assign to it as a destination, the same way as any other destination.
#Does this file tickets in a tracker from incidents?
No — Telegram is where your team works an alert in the moment. Notes and public status updates written anywhere are posted as replies under the alert so the group sees them, but ticket tracking happens in a connected tracker, not here.
#What do I need before connecting Telegram?
You'll add the InfraNest bot to the chat and send /start there, in that order — see the setup guide.
Let the group that gets woken up do something about it
Create your account, add your team’s Telegram group, and send it a test alert. There is nothing to copy.
Free plan · No credit card required · Set up in minutes