GitLab events, straight into Telegram
Every push, merge request, or pipeline result — posted to Telegram the moment it happens. No Telegram app to install, no monthly automation subscription.
The gap this fills: GitLab doesn't ship an official Telegram app. If you want push, merge request, or pipeline result 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
GitLab — Push
myorg/myrepo
· Fix login redirect bug
· Bump dependency versions
by Jane Doe
A real GitLab event, shown as ZestyGlue formats it for Telegram.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new GitLab → Telegram connector. You'll get a unique webhook URL right away.
- Point GitLab at it. In your project (or group) go to Settings → Webhooks, paste in your ZestyGlue webhook URL, and pick which trigger events to send.
- Set the secret token. GitLab lets you set a Secret token on the webhook — use the same one you enter into ZestyGlue's connector setup, so events can be verified as genuinely from your project.
- 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.
Under the hood: Unlike Stripe or Shopify, GitLab doesn't sign its payloads with HMAC — it sends a plain secret token in the X-Gitlab-Token header instead. ZestyGlue checks it with a constant-time comparison, so a timing attack can't be used to guess your token character by character.
Events you can forward
push
merge_request
issues
note (comments)
tag_push
pipeline
wiki_page
deployment
release
Questions
Is my GitLab Secret Token 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.
Can I forward events from a whole GitLab group, not just one project?
Yes — GitLab supports group-level webhooks, which fire for every project inside that group.
Will this show CI/CD pipeline failures?
Yes. Enable Pipeline events in the GitLab webhook configuration and ZestyGlue posts every status change.
Does this work with self-hosted GitLab?
Yes, as long as your GitLab instance can reach zestyglue.com over the internet to deliver the webhook.
How is my GitLab secret token stored?
Encrypted at rest, never logged, and never redisplayed after you enter it.
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 GitLab's side — GitLab 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.