NewsPRFlow is now a GitLab Technology Partner·What that means →

PRFlow

Your code review channel,
automated.

PRFlow posts every GitLab MR and GitHub PR to the Slack channel your team reviews in, keeps the card current, and shows what still needs a reviewer.

Get Started Free

Free for up to 3 users. No credit card required.

Works with GitHub, gitlab.com and self-hosted GitLab.

# dev-team
PRFlow 9:02 AM
#4809 · Fix flaky webhook retry test
:purple_heart: Merged into main
:file_folder: core-platform/integrations-api · :bust_in_silhouette: Sam Rivera (@samr) · fix/flaky-retry → main
PRFlow 9:14 AM
#4821 · Add rate limiting to webhook ingestion
:large_green_circle: CI passed
:red_circle: Approvals 1/2 — 1 more needed
:red_circle: 1 unresolved thread
:file_folder: core-platform/integrations-api · :bust_in_silhouette: Dana Gregory (@dgregory) · feat/webhook-rate-limit → main
SR2 repliesView thread

Actual PRFlow messages. Each card updates in place as its MR moves.

Red needs attention. Green is ready. Purple is merged.

The rail tells you the state before you read a word: which MRs still need someone, which are ready, which are done. One card per MR, recolored in place as it moves.

One merge request card in Slack moving through three states: red for needs attention (CI failed, 1 unresolved thread), green for ready for review (CI passed, all threads resolved), purple for merged. The same message, edited in place by PRFlow.

Why teams switch to PRFlow

See what you're missing with GitLab's official app

PRFlow vs Axolo·PRFlow vs PullNotifier·PRFlow vs Native GitLab Slack

Pipeline status
See CI/CD pass/fail in Slack
GitLab for Slack
PRFlow
Threaded comments
Comments in Slack thread
GitLab for Slack
PRFlow
One message per MR
Updates in place, no spam
GitLab for Slack
PRFlow
Self-hosted GitLab
Works with your own GitLab instance
GitLab for Slack
PRFlow
Review metrics
Cycle time, pickup time, and review load
GitLab for Slack
PRFlow
High channel noise
Flood your team with messages
GitLab for Slack
PRFlow

What PRFlow does

Exactly what's left to merge

The card lists every real merge requirement: approvals with counts, CI, unresolved threads, conflicts. Each one flips from red to green as it's satisfied.

One live card per MR

Opened, reviewed, approved, merged. The same Slack message updates in place through the whole lifecycle. No notification spam, ever.

CI/CD status included

Pipeline status lives on the card itself: running, passed, or failed. Know if builds are green without leaving Slack.

Comments in the thread

GitLab review comments flow into the card's Slack thread automatically, and edited comments update in place. The channel stays clean.

Scheduled digests

A per-channel summary of open MRs on your schedule, grouped into needs attention, waiting on review, and ready to merge, with stale MRs flagged.

GitHub works too

Install PRFlow from the GitHub Marketplace and pull requests get the same live card, with checks from GitHub Actions. No webhook setup needed.

Review metrics

A Metrics page for one repository or the whole org: review cycle time split into pickup, review, and approval-to-merge, merged count and first-pass rate by week, and review load per reviewer. Any range up to 90 days.

How teams use PRFlow

Pick the one that sounds like your team.

Your team posts PRs to a channel by hand

Someone pastes the link and asks for eyes, every time. PRFlow does the posting, keeps every card current, and shows what still needs a reviewer.

Read more

You are the one asked what is shipping today

See every open merge request at a glance, with CI status, approvals and what's stuck, without living in twenty GitLab tabs.

Read more

Every MR waits for its author to share it

Stop copy-pasting MR links and asking "can someone review?". Every MR posts itself to the right channel and stays up to date.

Read more

AI tools open more MRs than review keeps up with

More MRs, faster, bigger. PRFlow keeps every change visible so human review stays fast, accountable, and never rubber-stamped.

Read more

Simple pricing

Every feature included on every plan, even the free one.

Free
$0/month
  • Up to 3 users
  • All features included
  • Unlimited repositories and channels
Pro
$4/user/month
  • Unlimited users
  • All features included
  • 14-day free trial

Enterprise: SSO (SAML or OIDC), priority support, signed DPA — contact us.

See full pricing details →

Frequently asked questions

Setup, permissions, self-hosted GitLab, and how PRFlow compares

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.

Does PRFlow work with self-hosted GitLab?

Yes. PRFlow supports both gitlab.com and self-hosted GitLab. Connect with an 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 hello@prflow.dev if your instance has strict network restrictions.

What permissions does PRFlow need in GitLab, GitHub, 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. On GitHub, the PRFlow App requests four read-only permissions — pull requests, checks, issues, and repository metadata — and has no access to your code. In Slack, PRFlow uses a bot token obtained via OAuth to post and update messages in your chosen channels.

Does PRFlow work with GitHub?

Yes. Install PRFlow for Slack from the GitHub Marketplace, choose which repositories post to which Slack channel, exactly like GitLab projects. Each pull request gets the same live card that updates in place, with CI status from GitHub Actions and other check providers, and PR comments sync into the Slack thread just like GitLab.

Does PRFlow show review metrics?

Yes. The Metrics page in the PRFlow app shows review cycle time from open to merge, split into pickup, review, and approval-to-merge, alongside merged count and first-pass rate by week and review load per reviewer. Scope it to one repository or the whole organization and pick any range up to 90 days. On GitLab, approval-based numbers count from the day you connect, because GitLab approval history can't be imported.

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.

One card. Every state. Zero spam.

Red needs attention, green is ready, purple is merged — the same message, updated in place the whole way through. Connect GitLab or GitHub to Slack in minutes.

Get Started Free