PR notifications
that actually work

How do I stop GitLab from spamming my Slack channel?

Replace GitLab's official Slack app with PRFlow for merge request notifications. GitLab for Slack sends a separate message for every MR event (opened, pipeline, comment, approved, merged). PRFlow sends one message per MR that updates in place, so your channel stays readable.

How do I get one Slack message per merge request instead of many?

PRFlow posts a single Slack message when a merge request is opened, then updates that same message as the MR progresses — pipeline status, approvals, and merge all appear on the original message. Comments go to a Slack thread. No duplicate messages.

How do I see GitLab code review comments in a Slack thread?

PRFlow automatically syncs GitLab merge request comments into a Slack thread attached to the MR notification. When someone comments on your MR in GitLab, the comment appears in the thread. Edited comments are updated in place.

Is there an Axolo for GitLab?

Yes, Axolo supports GitLab with features like one-message-per-MR (team channels mode) and CI/CD notifications. PRFlow is a GitLab-only alternative — also one updating message per MR with CI/CD status and threaded comments, but completely free during beta with no seat limits. See the full PRFlow vs Axolo comparison.

Is there a Pullnotifier for GitLab?

Pullnotifier only supports GitHub. PRFlow is built specifically for GitLab and delivers similar functionality — Slack notifications for merge requests with CI/CD pipeline status and threaded code review comments. See the full PRFlow vs Pullnotifier comparison.

Does PRFlow work with self-hosted GitLab?

Yes. PRFlow supports both gitlab.com and self-hosted GitLab. Connect with a read-only access token and PRFlow automatically discovers MR changes. Optionally add a webhook for real-time notifications.

How does PRFlow handle self-hosted GitLab behind a firewall?

PRFlow needs to reach your GitLab API over HTTPS to poll for MR updates. If you also want real-time notifications, add a webhook — your GitLab needs outbound HTTPS to app.prflow.dev for that, but webhooks are optional. Contact us if your instance has strict network restrictions.

What permissions does PRFlow need in GitLab and Slack?

In GitLab, PRFlow needs a personal access token with read_api scope to read merge request data and comments. For gitlab.com, you can also use OAuth. In Slack, PRFlow uses a bot token obtained via OAuth to post and update messages in your chosen channels.

How is PRFlow different from GitLab's official Slack app?

GitLab for Slack sends a new message for every event — 10+ messages per merge request. PRFlow sends one message per MR that updates in place, shows CI/CD pipeline status inline, and syncs review comments to a Slack thread. GitLab for Slack also supports slash commands and issue notifications, which PRFlow does not.