Telegram Integration
PingSLA supports Telegram notifications via bot messages. Alerts can be sent to personal chats, groups, or channels.
Setup: Personal Chat
- Open Telegram and search for @PingSLABot
- Start a chat:
/start - The bot will display your Chat ID
- In PingSLA: Settings → Notification Channels → New Channel → Telegram
- Enter the Chat ID
- Click Test to confirm
Setup: Group or Channel
For team notifications, add the bot to a group or channel:
Group Setup
- Add @PingSLABot to your Telegram group
- Send any message in the group to wake the bot
- Get the Chat ID by running
/idin the group - Enter the Chat ID in PingSLA (group IDs are negative, e.g.,
-1001234567890)
Channel Setup
- Create or open your Telegram channel
- Add @PingSLABot as an administrator (requires "Post Messages" permission)
- Get the channel username or ID
- Enter in PingSLA (format:
@yourchannelnameor-100xxxxxxxxxx)
Chat ID Format
| Target | ID Format | Example |
|---|---|---|
| Personal chat | Positive integer | 123456789 |
| Group | Negative integer | -123456789 |
| Supergroup | Negative with 100 prefix | -1001234567890 |
| Channel username | @name | @ops_alerts |
Notification Format
🔴 INCIDENT ALERT — PingSLA
Monitor: Production API Health
Status: DOWN
Reason: HTTP 503 Service Unavailable
Time: 2026-05-18 14:32 UTC
🔗 https://app.pingsla.com/incidents/inc_xxx
✅ RECOVERED — PingSLA
Monitor: Production API Health
Status: UP
Downtime: 4m 22s
Time: 2026-05-18 14:36 UTC
🔗 https://app.pingsla.com/incidents/inc_xxx
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Bot doesn't respond | Bot not started | Send /start to the bot first |
| No messages in group | Bot not in group | Add @PingSLABot to the group |
| Wrong Chat ID | ID copied incorrectly | Use /id command in the group/chat |
| Channel not receiving | Bot not admin | Make bot an admin with post permission |
| Test passes, incidents don't | Alert policy not attached | Verify monitor has a policy with this channel |