Telegram incident notifications
Updated 2026-10-22 · Pharos 1.0.1
Telegram is a destination since Pharos 0.5.9. If it is missing under Add a destination, update Pharos first.
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 Integrations & API, then Send out.
- Under Add a destination pick Telegram and enter a Name in Pharos.
- Paste the Telegram bot token.
- Under Chat ID or public channel 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.
- Press Save and 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 list of destinations. To replace the token or the chat, remove the destination 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 the Delivery log.
See the Telegram sendMessage API and Pharos scheduler guide.