Telegram incident notifications
Updated 2026-09-09 · Pharos 0.6.0
Available in the upcoming Pharos release. If Telegram is missing under Shape, your installed version does not contain this feature yet.
Create a bot
Create a bot with @BotFather and copy its token. Start a conversation with the bot for personal notifications. For a group or channel, add the bot with permission to send messages; channel posting requires administrator permission.
Add the notification
- Open Admin → Integrations → Notifications.
- Enter a Name and select Telegram under Shape.
- Paste the Telegram bot token.
- Enter the numeric Chat ID, keeping the minus sign for groups, or a public channel @username. A personal username cannot replace a numeric chat ID.
- Click Add notification, then Send test. Confirm receipt in the intended Telegram destination.
No webhook Address is needed: Pharos builds the Telegram API address. The token is stored encrypted and masked in the notification list. To replace the token or destination, remove the notification and add it again.
Delivery and retries
Messages contain the incident status, title and status-page link as plain text. Opened, updated and resolved incidents are queued for the minute scheduler. Temporary failures retry up to six total attempts with increasing delays. Telegram rate limits respect the API retry delay. Send test makes one immediate attempt and is not queued.
If nothing arrives
- HTTP 400: check the destination chat ID and bot membership.
- HTTP 401 or 404: check whether the bot token is correct and still valid.
- HTTP 403: start the personal chat, unblock the bot or grant permission to post.
- HTTP 429: queued messages wait for the Telegram retry delay.
- Connection failure: check outbound HTTPS, DNS and TLS access to api.telegram.org.
- Test succeeds but incidents do not arrive: check the minute scheduler and delivery history under Integrations.
See the Telegram sendMessage API and Pharos scheduler guide.