GitHub events, straight into Telegram
Every push, pull request, issue, or release — posted to Telegram the moment it happens. No Telegram app to install, no monthly automation subscription.
The gap this fills: GitHub doesn't ship an official Telegram app. If you want push, pull request, issue, or release to show up in Telegram the moment it happens, the usual options are a paid third-party bot, custom code, or routing everything through a $20–50/month automation platform just to move one webhook from one URL to another. ZestyGlue does exactly that one thing for $9/month.
What it looks like
ZestyGlue
GitHub — Push
myorg/myrepo
· Fix login redirect bug
· Bump dependency versions
by janedoe
A real GitHub event, shown as ZestyGlue formats it for Telegram.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new GitHub → Telegram connector. You'll get a unique webhook URL right away.
- Point GitHub at it. In your repo (or org), go to Settings → Webhooks → Add webhook, paste in your ZestyGlue webhook URL, set content type to application/json, and pick the events you want.
- Set the secret. GitHub lets you set a Secret on the webhook — use the same one you enter into ZestyGlue's connector setup, so events can be verified as genuinely from your repo.
- Point Telegram at ZestyGlue. Message @BotFather to create a bot and copy its token. Add the bot to your group or channel, then find its chat ID (e.g. via @userinfobot) and enter both into ZestyGlue.
Tip: GitHub sends a separate signed request per event type you enable — most teams start with just push and pull_request, then add issues or release later once the channel proves useful.
Events you can forward
push
pull_request
issues
release
star
Questions
Is my GitHub Webhook Secret safe with ZestyGlue?
It's encrypted at rest with Fernet symmetric encryption before it ever touches disk, it's never logged, and it's never displayed again in the dashboard after you enter it — only a masked placeholder is shown.
Does this work with GitHub organizations, not just personal repos?
Yes — organization-owned repos and org-level webhooks work the same way as personal repos.
Can I forward events from more than one repo to the same channel?
Yes — add the same ZestyGlue webhook URL to as many repos as you like; every one of them will post into the same destination.
Does self-hosted GitHub Enterprise work the same way?
Yes, as long as your GitHub Enterprise instance can reach zestyglue.com over the internet to deliver the webhook.
Does the bot need to be an admin in my group?
No, a regular member is enough for the bot to post messages. Admin rights are only needed for things like pinning messages, which ZestyGlue doesn't do.
What happens if my ZestyGlue subscription lapses?
Events are silently dropped rather than causing errors on GitHub's side — GitHub never sees a failure response, so it won't retry aggressively or flag your webhook as broken. Your dashboard will simply stop showing new events until you resubscribe.