Telegram Integration
Receive uptime alerts, incident reports, and recovery notifications directly in your Telegram chat — private or group.
Connect Your Telegram Account
The entire setup takes under two minutes. You'll need your Telegram chat ID and the StatusPulse bot added to your conversation.
1. Find Your Chat ID
Open Telegram and start a conversation with @StatusPulseBot. Send the command /getid. The bot replies with your numeric chat ID (e.g., 482910573). For group chats, add the bot to the group first, then run /getid inside the group.
2. Add the Bot to Your Chat
Search for @StatusPulseBot in Telegram and press Start. For group alerts, invite the bot by username — it appears as "StatusPulse Monitor" with a purple icon. The bot must have the Post Messages permission in group settings.
3. Link the Chat in Your Dashboard
Go to Settings → Notifications → Telegram in your StatusPulse dashboard. Paste the chat ID you received, select the alert severity levels (Critical, Warning, Recovery), and click Save Integration. A confirmation message arrives in Telegram within 10 seconds.
You can link multiple Telegram chats to a single account — one for on-call engineers, another for the management channel. Each chat receives independent alert routing.
Control Alerts from Telegram
Manage your monitoring directly from the chat. The bot supports the following commands:
/status
Returns a summary of all monitored endpoints with their current state (Operational, Degraded, Down), last check timestamp, and response time. Example output: api.example.com — Operational (42ms) | status.example.com — Degraded (1200ms).
/mute <duration>
Temporarily suppress alerts for a specified duration. Accepts values like 15m, 1h, 24h. Useful during planned maintenance windows. The bot confirms the mute period and notifies when it expires.
/ping <endpoint>
Triggers an immediate check on a specific endpoint and reports the result in chat. Example: /ping api.example.com returns Response: 200 OK | Latency: 38ms | Checked at: 2025-01-15 14:22 UTC.
/history <endpoint>
Displays the last 5 incidents for the specified endpoint, including downtime duration, recovery time, and SLA impact. Requires the endpoint to be linked to your account.
/help
Lists all available commands with brief descriptions and usage examples. Always available, even when alerts are muted.
/unmute
Immediately cancels an active mute period. Alerts resume for all severity levels configured in your dashboard. The bot posts a Alerting restored message to confirm.
What Alerts Look Like in Telegram
Every notification follows a consistent structure so you can scan and act quickly. Here's how a typical alert is formatted:
Critical Alert Example
🔴 CRITICAL — api.example.com is Down
Endpoint: https://api.example.com/v2/health
Expected: 200 OK — Received: Connection timed out
Detected at: 2025-01-15 09:14:03 UTC
Last successful check: 2025-01-15 09:12:01 UTC (87ms)
Consecutive failures: 2 of 3
Reply /ping api.example.com to recheck or /mute 30m to suppress.
Recovery Alert Example
🟢 RECOVERED — api.example.com is Operational
Endpoint: https://api.example.com/v2/health
Downtime duration: 4 minutes 12 seconds
Restored at: 2025-01-15 09:18:15 UTC
Current response time: 91ms
SLA impact: None (within 5-minute threshold)
View full incident report in your StatusPulse dashboard.
Scheduled Downtime Notification
🟡 SCHEDULED — Maintenance on cdn.example.com
Window: 2025-01-16 02:00–04:00 UTC
Reason: SSL certificate rotation
Affected monitors: 3 (cdn.example.com, static.example.com, fonts.example.com)
Alerts suppressed during this window. No action required.
Required permissions: In group chats, the bot needs Post Messages and Pin Messages (optional, for pinning critical incidents). No admin rights are required. The bot does not read or store message content from your chat — it only sends outbound notifications and responds to commands prefixed with /.