.png&w=64&q=75){kind=small}
Slack PR notifications for GitHub Enterprise Server
The hosted GitHub Slack app only talks to github.com — it can’t reach your GHES instance. PullNotifier supports GHES, EMU, and air-gapped setups with the routing, reviewer mapping, and digests your platform team doesn’t have to build or maintain.
30-minute call · we scope your deployment model on the spot
Why GHES teams get stuck on Slack notifications
GitHub Enterprise Server runs in your own network — and that breaks the integrations everyone else takes for granted.
The hosted Slack app can’t reach GHES
The official GitHub app in the Slack App Directory only talks to github.com. It cannot subscribe to repositories on a GHES instance behind a VPN or in a private subnet — /github subscribe simply has nothing to connect to.
Self-hosting the open source bot is a project
You can clone github/slack-bot, expose a webhook endpoint reachable from your GHES instance, and run it yourself. It works — but your platform team now owns uptime, upgrades, and a bot that still lacks reviewer mapping, routing, and digests.
Compliance rules out most third-party tools
Tools that request repository contents access are a non-starter for regulated teams. You need an integration that reads PR metadata only — titles, reviewers, labels, status — and never your source code.
Three ways to run PullNotifier with GHES
From a managed connection through your proxy to a deployment that never leaves your network.
Managed integration
PullNotifier connects to your GHES instance as a managed service, including air-gapped setups where outbound traffic from GHES has to go through a proxy. Fastest to set up — no infrastructure on your side.
Dedicated infrastructure
Your own dedicated server and database, operated by us. Full feature set with hard tenant isolation for organizations that require it.
Fully self-hosted
Deploy PullNotifier inside your own network using our Docker container. Nothing leaves your infrastructure — the option for the strictest environments.
Everything the self-hosted bot doesn’t do
The open source github/slack-bot posts events. PullNotifier runs your review workflow.
Smart, scoped PR cards
Cards update in place as the PR moves through draft, review, changes requested, and merged. No new message every event.
Multi-channel routing
Route by repo, label, author, or branch across hundreds of repositories and teams — the frontend repo to #frontend-prs, hotfixes to their own channel.
Reviewer @-mentions that work
Map GitHub usernames to Slack handles in bulk so review requests actually ping people instead of rendering as plain text.
Enterprise Managed Users (EMU)
Full support for GitHub EMU organizations, with a dedicated setup flow and user-mapping handled for you.
Daily PR digest
A configurable morning summary of every open PR and its blocker. Standups get shorter, stale PRs get unstuck.
Personal notifications
DM engineers when they’re requested as a reviewer, when their PR is approved, or when changes are requested — with per-user conditions.
PullNotifier vs self-hosting the official bot
| Capability | Self-hosted github/slack-bot | PullNotifier |
|---|---|---|
| Works with GitHub Enterprise Server | ||
| Works behind a proxy / air-gapped | You build it | |
| You maintain the infrastructure | Yes — your platform team | Optional (self-hosted tier) |
| Reviewer → Slack user mapping | ||
| Multi-channel routing rules | ||
| Daily digests & reminders | ||
| EMU support | ||
| Dedicated support & setup help |
Enterprise Managed Users
Running an EMU enterprise? PullNotifier supports EMU organizations end to end — request setup from your dashboard and we configure the user mapping for you, typically within 4 to 8 business hours.
Read the EMU setup guideBuilt for security review
Read-only access to PR metadata — never repository contents or source code
Send-only Slack permissions — we never read your messages
Encryption in transit and at rest, data minimization by design
GitHub Enterprise Server FAQ
Does PullNotifier work with GitHub Enterprise Server?
Yes. PullNotifier supports GHES as a managed integration, including air-gapped setups where outbound traffic from your GHES instance has to go through a proxy. For the strictest environments, PullNotifier can also run fully self-hosted inside your network via a Docker container, or on dedicated infrastructure we operate for you.
Does the official GitHub Slack app support GitHub Enterprise Server?
Not the hosted one. The GitHub app in the Slack App Directory only talks to github.com, so it cannot reach a GHES instance behind a VPN or in a private subnet. Your options are self-hosting the open source github/slack-bot yourself, or using a managed integration like PullNotifier that supports GHES.
Do you support GitHub Enterprise Managed Users (EMU)?
Yes. EMU organizations are fully supported. Setup involves a short request flow — we configure the mapping for your organization, typically within 4 to 8 business hours, and notify you when it is ready. See the EMU setup guide for the step-by-step.
Can PullNotifier access our source code?
No. PullNotifier requests minimal, read-only GitHub permissions and only reads pull request metadata — titles, descriptions, labels, reviewers, and review status. It has no access to repository contents, source code, or file changes. The security page lists every permission and why it is requested.
Can PullNotifier run entirely inside our network?
Yes. The self-hosted option deploys PullNotifier within your own infrastructure using our Docker container, so both your GHES instance and the integration stay inside your network boundary.
How is the GitHub Enterprise Server plan priced?
GHES, dedicated-infrastructure, and self-hosted deployments are on the Enterprise Server plan with custom pricing based on team size and deployment model. Book a demo and we will scope it in one call.
Get GHES pull requests into Slack this week
One call to scope your deployment — managed, dedicated, or self-hosted. See pricing or the complete GitHub Slack integration guide for the full background.