Guide · GitHub → Telegram · Verified November 1, 2026

GitHub to Telegram webhook guide

Short answer: One GitHub endpoint verifies each delivery, a destination filter keeps the events in this guide, and every match is delivered to Telegram with its own retry schedule and delivery log.

The on-call rotation already lives in Telegram. One GitHub endpoint collects issues from a repository and one destination posts them into the triage chat, so nobody has to add the responder to GitHub to see what broke — and the delivery log keeps the issue link that started the alert.

At a glance

1. Configure the GitHub webhook

  1. In the repository, open Settings → Webhooks → Add webhook and paste the endpoint's ingestion URL.
  2. Set Content type to application/json and paste the same signing secret the endpoint uses.
  3. Choose “Let me select individual events” and enable Issues, Issue comments, Pull requests, Pushes, Releases, and Workflow runs as needed.
  4. Open or label an issue to send the first delivery, then check the delivery log.

HMAC-SHA256 over the raw request body, compared in constant time. No timestamp header, so there is no clock-window check.

2. Filter to the events that matter

Filters run per destination before rendering, so a non-matching event is stored with no delivery and no agent call. The rules below are the difference between a useful pairing and a noisy one.

Filter: new issues only

{
  "allow": [
    { "field": "event.type", "op": "equals", "value": "issues.opened" }
  ],
  "senders": {
    "allow": { "associations": ["OWNER", "MEMBER", "COLLABORATOR"] }
  },
  "ignoreBots": true
}

3. Configure the Telegram destination

A Hooks Telegram destination calls sendMessage with your bot token and a chat id; the token stays in a project secret. The message text renders from the event, and Telegram's ok flag decides success even when the HTTP status is 200.

Destination: Telegram bot

{
  "token": "{{secret.TELEGRAM_BOT_TOKEN}}",
  "chatId": "-1001234567890",
  "text": "<b>{{event.subject.title}}</b>\n{{event.subject.url}}",
  "parseMode": "HTML"
}

Secrets enter configs only as {{secret.NAME}} references; literal credentials are rejected. Full Telegram target guide

4. Verify the delivery and its retries

Send one real event from the source, then open Deliveries. A 2xx from the target means accepted, not finished. 408, 425, 429 and 5xx retry with backoff honoring Retry-After; other 4xx fail permanently with a named code. The rendered request is stored per attempt, so a bad field path is visible without re-sending.

Hooks delivery detail: attempt timeline, request payload, and the destination response for one delivery
Delivery detail: the attempt timeline, the rendered request the target received, and its response — the same record an event keeps for every destination.

The pitfall this pairing hits

HTTP 200 does not mean Telegram accepted the message. Telegram reports bot failures as HTTP 200 with ok: false and an error_code, for example chat not found when the bot was never added to the group. Hooks reads the body and records a failed delivery, so a green status in Telegram's own dashboard is not evidence the message was delivered.

Frequently asked questions

Do I need one endpoint per source or one per destination?

One endpoint per source. Each destination under that endpoint carries its own filter, template, retry schedule, and delivery log, so the same event can feed several targets without duplicate ingress URLs.

What happens while the target is down?

Retryable failures back off and retry within the destination's window; permanent 4xx failures stop immediately. Either way, the original event stays stored, so after fixing the target you replay the event instead of asking the source to send it again.

HTTP 200 does not mean Telegram accepted the message

Telegram reports bot failures as HTTP 200 with ok: false and an error_code, for example chat not found when the bot was never added to the group. Hooks reads the body and records a failed delivery, so a green status in Telegram's own dashboard is not evidence the message was delivered.

More GitHub guides

Other ways into Telegram