
Gitlab
Forwards notifications from GitLab (both gitlab.com and self-hosted instances) into Telegram and lets you respond quickly, complementing GitLab's official Slack-style integrations. Free, English interface.
Key features
- Notifications from both gitlab.com and self-hosted GitLab
- Quick responses to events from the chat
- Fits pipeline, merge request and comment updates
Gitlab
This bot's own description is explicit about what it does: receive notifications from GitLab, cloud or self-hosted, and let you respond to them quickly from Telegram. That put it in the same space as GitLab's documented Telegram integration, which itself relies on a bot token and webhook configured per project — this bot appears to offer a similar bridge without necessarily requiring you to run your own bot instance.
For a team already using GitLab CI/CD and merge requests as their daily workflow, having pipeline results, new merge requests and comment threads land in a Telegram chat cuts the number of tabs open during a working day. Because GitLab supports both the hosted gitlab.com and self-hosted GitLab installations, a notification bridge that handles both is more broadly useful than one tied to a single hosting mode.
As with most notification-relay bots, expect to do the actual event configuration — which projects, which event types — inside GitLab's own integration settings rather than through bot commands; the Telegram side is the delivery endpoint.
How to start
- Open @gitlab_bot and press Start to get your chat ID
- In your GitLab project, open Settings → Integrations → Telegram
- Paste the bot token and chat details to start receiving events
Commands
/startShow your chat ID and setup instructionsPricing and limits
Free
Pros / Cons
- Works with both cloud and self-hosted GitLab
- Free
- Bot profile has no bio card beyond the short tagline
- Event configuration happens in GitLab, not in the bot
Score breakdown
| Criterion | Weight | Points | |
|---|---|---|---|
| Functionality | 25 | 6 / 10 | |
| Reliability & speed | 15 | 6 / 10 | |
| Popularity & trust | 15 | 5 / 10 | |
| Price & free tier | 10 | 10 / 10 | |
| Usability | 10 | 6 / 10 | |
| Safety & privacy | 10 | 7 / 10 | |
| Freshness | 5 | 5 / 10 | |
| Localization | 5 | 3 / 10 | |
| No intrusive ads | 5 | 10 / 10 | |
| Score | 100 | 63.0 |
Alternatives
All alternatives →
Notifine for GitLabThe GitLab half of Notifine, an open-source notification bridge (also covering GitHub and Trello) that posts…
GitHubA long-running bot that subscribes to public GitHub repositories and posts new issues, pull requests, pushes…
Github Release BotNotifies a chat whenever a public GitHub repository publishes a new release, useful for tracking…CircleCIReports CircleCI build statuses into Telegram, so a pipeline pass or failure shows up in chat instead of…FAQ
Does it work with self-hosted GitLab, not just gitlab.com?
Yes, the bot's own description explicitly mentions both cloud and hosted versions.
Technical details
- Inline mode
- Mini App
- Works in groups
- Works in channels
- Accepts voice
- Accepts files
- Requires phone number
- Requires registration
- Shows ads
- Works in Russia without VPN