4.8 Stars on G2★★★★★

The Ultimate GitLab & Slack integration

Smart merge request notifications your team will actually read. One message per MR, updated live, in the right Slack channel.

Works on GitLab Free · gitlab.com groups · No credit card required

feat: Add rate limiting to webhooks
!42 opened by chloe
fix: Stabilise flaky pipeline on merge trains
!43 opened by amara
chore: Bump CI templates and images
!44 opened by bot
# general
# random
# team-frontend
3
# team-api
12
# hotfixes
5

Trusted by over 30,000+ engineers across 1,000+ orgs.

Game Changer. It covers 99.9% of PR workflows while keeping notifications targeted to only those who need it. The other 0.1% of edge cases is quickly shrinking as they have responded to feature requests super quickly.

Matthew A.

Principal Engineer

G2Read on G2 →

Everything the GitHub integration does, now for GitLab.

The notification engine 30,000+ engineers rely on, now speaking merge requests: same smart threading, same routing, same noise controls.

One message per merge request

Each MR gets a single Slack message that updates in place, so there is no channel spam. Merged, closed, draft, and reviewer changes all edit the same message.

Approvals & comments as thread replies

Approvals, inline diff comments, and discussion replies land in the MR message’s thread, so the channel stays readable and the context stays together.

Multi-channel routing

Route MRs to different channels by label, author, or reviewer, per project or group-wide. The frontend team’s MRs go to #frontend, hotfixes to #urgent.

GitLab ⇔ Slack user mapping

Map GitLab users to Slack users once and reviewers get proper @-mentions instead of plain-text usernames.

Daily digests

A scheduled channel summary of stale MRs and MRs still waiting on approvals, so nothing sits unreviewed for days.

Personal DM notifications

Review requested? MR approved? Someone mentioned you? Get a direct message for the events that involve you personally.

Noise controls

Draft MRs are skipped until they’re ready. Mute by target branch, blacklist bot authors, and filter comment notifications by content.

Works on GitLab Free

Per-project webhooks mean no Premium or Ultimate requirement and no group-webhook paywall. Subgroups are fully supported.

Set up in three steps

From zero to threaded merge request notifications in under five minutes.

1

Log in with GitLab

One-click OAuth with your gitlab.com account. No tokens to paste, no YAML to write.

2

Pick your group and projects

Choose the projects to notify on (Maintainer role required). PullNotifier registers the webhooks for you.

3

Connect Slack

Authorize the Slack app, pick a channel, and your next merge request shows up formatted and threaded.

Frequently asked questions

Log in to PullNotifier with your gitlab.com account, pick a group and the projects to notify on, then authorize the Slack app and choose a channel. Webhooks are registered automatically, with no YAML and no tokens to paste. The whole setup takes under five minutes.

Yes. PullNotifier uses per-project webhooks, which are available on every GitLab tier. Group webhooks (a Premium feature) are not required.

The official GitLab for Slack app posts a separate message for every event, which quickly floods the channel. PullNotifier keeps one live-updating message per merge request, moves approvals and comments into its thread, routes MRs to the right channel by label, author, or reviewer, and adds daily digests and personal DMs.

Merge request opened, reopened, merged, closed, draft/ready transitions, title edits, new commits, reviewer and assignee changes, label changes, approvals, inline diff comments, and discussion comments.

Yes. Multi-channel routing sends MRs to different channels by label, author, or reviewer, per project or group-wide. The frontend team’s MRs go to #frontend, hotfixes to #urgent.

Yes. Connect a group and pick projects from any of its subgroups.

Not yet. gitlab.com is supported today. Self-managed support is on the roadmap; contact us if your team needs it.

GitLab support is Slack-only for now. Teams delivery for GitLab is planned, and GitHub + Teams is already supported.

GitLab has a "Request changes" review action, but the platform fires no webhook and exposes no API state when a reviewer uses it, so no integration can detect that event (tracked upstream as GitLab issue #592358). Approvals, comments, and every other review signal come through normally, and we will add notifications the moment GitLab ships the event.

Yes. It is free for teams with fewer than 4 developers. Larger teams get a 14-day free trial with no credit card required.

Ship faster with fewer pings

Your next merge request can be a tidy, threaded Slack message. Set up in minutes.

Continue with GitLab
14-day free trial No credit card required