PRFlow

GitHub pull requests in Slack. Always know what's blocking merge.

Checks, reviews, and what's left before merge — live in the channel each team already watches. Reviews get picked up sooner, and nobody opens GitHub just to find out why something stalled.

Connect GitHub to Slack

Only reads pull requests, checks, and repository metadata. Never your code.

Free for up to 3 users. Listed on the GitHub Marketplace.

# platform-team
PRFlow 9:52 AM
#485 · Cache org lookups in the token refresh path
Checks passed
Reviews 1/2 — 1 more needed
acme/platform-web · Dana Gregory (@dgregory) · perf/org-lookup-cache → main
SR3 repliesView thread
PRFlow 11:47 AM
#479 · Fix flaky retry test in webhook consumer
Merged into main
acme/platform-web · Sam Rivera (@samr) · fix/flaky-retry → main

More pull requests. The same reviewers.

Coding agents raised how many pull requests a team opens. Nobody's review capacity moved. So the queue grows, and every pull request waits longer for its first review.

The expensive part is the wait: the pull request nobody has noticed, and the reviewer who would have looked an hour ago had they seen it go up. PRFlow puts the ask in the channel the team already reads, with its state attached.

One card per pull request. Always the current state.

The channel shows what's open and what each one is waiting on, instead of a scroll of state changes nobody reads.

Waiting on a second review
PRFlow 9:14 AM
#482 · Add rate limiting to webhook ingestion
Checks passed
Reviews 1/2 — 1 more needed
acme/platform-web
Ready to merge
PRFlow 9:14 AM (edited)
#482 · Add rate limiting to webhook ingestion
Checks passed
Reviews 2/2
acme/platform-web
Merged
PRFlow 9:14 AM (edited)
#482 · Add rate limiting to webhook ingestion
Merged into main
acme/platform-web

How it works

01

Install the GitHub App

From Settings → Connections in PRFlow, or straight from the GitHub Marketplace. Pick the organization and which repositories it can see.

02

Write a routing rule

Connect Slack, then add a rule: match one repository or a pattern like acme/platform-*, and pick the channel it posts to. Rules run in order, so repositories created later route themselves.

03

Every pull request posts itself

Opened, reviewed, checked, merged — the channel stays current on its own. Comments sync to the pull request's thread, so the discussion is one click away.

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

A user is any pull request author whose PR triggers a notification in a given billing period. Reviewers and commenters who never open one don't count.

See full pricing details →

PRFlow never sees your code

No Contents permission, no write access anywhere. It cannot read your repository, your diffs, or your history, and it cannot change anything on GitHub.

What it reads, all read-only: pull requests, checks, and repository metadata. That is the entire list.

Pull request comments come through that first scope, which is how comment sync works. PRFlow reads them and relays them to Slack. It never reads the code they are attached to.

Every webhook delivery is signature-verified before it is processed.

Frequently asked questions

Permissions, setup, and what you need to install

I already get PRs in Slack. What's different?

Most integrations post an event — opened, reviewed, merged — so a busy channel becomes a scroll of state changes and people mute it. PRFlow posts one card per pull request and updates that card in place, so the channel shows what is open and what each one is waiting on, rather than a history of what happened.

What permissions does the PRFlow GitHub App need?

Three read-only permissions: pull requests, checks, and repository metadata. There is no Contents permission and no write access anywhere, so PRFlow cannot read your code or change anything on GitHub.

Does PRFlow support GitHub Enterprise Server?

Not yet. PRFlow's GitHub App connects to github.com organizations and personal accounts. If your team runs GitHub Enterprise Server, email hello@prflow.dev and we'll work with you on it.

What do I need to install PRFlow for GitHub?

Just the GitHub App. Install PRFlow for Slack from the GitHub Marketplace, choose which repositories it can see, then connect Slack and add a routing rule. There is no webhook URL or secret to configure.

Ready to make the channel legible again?

Install the GitHub App, add one routing rule, and the next pull request your team opens shows up in the channel. Free for up to 3 users.

Connect GitHub to Slack

Also on the GitHub Marketplace.