GitLab bot for Lark
Teams on GitLab often run self-managed instances and multiple pipelines. The GitLab bot connects through project webhooks and posts MR, issue and pipeline changes to Lark, without another notification dashboard.
What it solves
- A merge request waits for review without reaching the reviewer.
- A failed pipeline is fixed later than it should be.
- Self-managed GitLab notifications are limited, so the team falls back to email.
Core capabilities
MR and issue notifications
MR creation, merge, close, issues and comments are posted per project.
Pipeline results
Pipeline success, failure and cancellation land in the group with the job link.
Self-managed support
Works through project webhooks, including self-managed GitLab instances.
Project-level subscriptions
Each project can target its own group and event scope.
How to connect
- Add the bot to the Lark group and get its webhook URL.
- Configure the event source, target group and notification rules.
- Send a test event and confirm the message and @mention.
This page does not show the internal console. Configuration details and permissions are provided during onboarding, or contact sales to learn more.
Who it is for
- Engineering teams
- DevOps and platform teams
- Companies running self-managed GitLab
FAQ
Can self-managed GitLab connect?
Yes. As long as the GitLab instance can reach the bot endpoint, project webhooks can be configured.
Can we only notify on pipeline failures?
Yes. Configure the event scope to keep only failures or key branches.
Related capabilities and solutions
Bring this capability into your Lark groups
Tell us about your team and use case. We will recommend SaaS or self-hosted deployment.