# PRFlow

> GitLab merge request notifications in Slack. One updating message per MR with CI/CD status and threaded comment sync.

PRFlow replaces GitLab's official Slack integration for merge request notifications. Instead of flooding channels with separate messages for every MR event, PRFlow posts a single message per merge request that updates in place as the MR progresses.

## Key Features

- One updating Slack message per merge request (not 10+ separate messages)
- CI/CD pipeline status displayed inline on the notification
- GitLab review comments synced to a Slack thread
- Works with gitlab.com and self-hosted GitLab
- Read-only GitLab access (read_api scope only — no write permissions)
- Posts to your existing Slack channels (no ephemeral channels)
- Multi-tenant: supports multiple GitLab instances and Slack workspaces

## Use Cases

- Teams using GitLab for code review who communicate in Slack
- Organizations migrating from GitHub to GitLab who miss PullNotifier-style notifications
- DevOps teams who want CI/CD pipeline visibility in Slack without noise

## Links

- [Homepage](https://prflow.dev)
- [Blog](https://prflow.dev/blog/)
- [GitLab for Slack vs PRFlow comparison](https://prflow.dev/blog/gitlab-slack-comparison)
- [PRFlow vs Axolo](https://prflow.dev/alternatives/axolo-for-gitlab)
- [PRFlow vs PullNotifier](https://prflow.dev/alternatives/pullnotifier-for-gitlab)
- [Sign In / Get Started](https://app.prflow.dev)
- [Privacy Policy](https://prflow.dev/privacy.html)
- [Terms of Service](https://prflow.dev/terms.html)
- [Contact](mailto:hello@prflow.dev)

## Pricing

Free during beta. No credit card required.