pullping.Request access
GitHubSlackFinally on the same page.

One PR. One Slack message.
Always up to date.

From draft to merged, follow every next step in one Slack message.
Current status. Clear approvals. Less chasing.

Request access Watch the tour
Made for GitHub. At home in Slack.
Product tour26 seconds. Fictional team.

An animated tour in four chapters. First, without PullPing, six separate notifications arrive for one pull request. Second, with PullPing, one Slack message updates in place from Draft to Needs review, Ready, and Merged, and keeps its timestamp. Third, adding a GitHub label moves the message to that team’s channel and removes it from the fallback channel. Fourth, the /pullping digest command lists open pull requests with the next step for each.

ONE PULL REQUEST. ONE LIVING MESSAGE.Your workflow, with a little less work.

LESS ADMIN. MORE MOMENTUM.

Great work gets stuck
between “opened” and “merged.”

PullPing keeps the next step clear, so your team can keep moving.
No new dashboard. No more “did you see my PR?”

The whole story.
One message.

From opened to merged, the same Slack message stays current. Context stays together. Your channel stays quiet.

Updated, not repeated

The right repo.
The right people.

Route repositories to the channels that own them. Connect GitHub accounts to Slack for mentions that reach your team.

A place for every project

Your next move.
Already clear.

See what needs a review, an author update, or a merge. Check your queue or schedule a daily team digest.

Less checking, more doing
SMALL SETUP. EVERYDAY DIFFERENCE.

Fits right into
how you work.

You already have the tools.
PullPing connects the dots.

Let’s get you connected
01

Make room in Slack.

Add PullPing to your workspace and invite it to your team’s channel.

02

Bring your repositories.

Use an existing GitHub App installation, or install it for your approved repositories. Connect GitHub from Slack setup and approve repository-name sharing. Complete verification to save the workspace link.

03

Connect. Then get back to it.

Select a repository and Slack channel, then save the route. Route admins can also use this command in the destination channel.

/pullping route owner/repo

Your code stays in GitHub.
Your team stays in the loop.

PullPing reads PR activity and brings the useful parts to Slack.
Your reviews and merges stay exactly where they belong.

See how it works
HOSTED PAID ACCESS

Start simple.
Keep reviews moving.

Early access starts at $29 per Slack workspace each month. Access is invite-only, with manual approval and billing.

EARLY ACCESS$29 / workspace / month
  • Up to 10 routing rules
  • Unlimited Slack users
  • Manual billing during early access
See pricing
A FEW GOOD QUESTIONS

The little
details.

More curious?
Read the docs

What does PullPing actually do?

PullPing brings GitHub pull request activity into Slack. It keeps one message current as a PR changes. Your team sees the status, the next action, and the right people to involve.

Will this add more noise to our channels?

PullPing updates the existing PR message instead of creating a new message for each change. Routed draft PRs can appear before review. Meaningful updates stay in the PR thread.

Can we choose which repositories go to each channel?

Choose a repository and channel in setup, or use /pullping route owner/repo in Slack. Use /pullping route-label owner/repo label-name for monorepo teams. Matching label routes override the repository fallback; routing uses labels, not file paths.

Who can connect a GitHub organization?

A person with PullPing route-admin access and active organization owner status must complete the connection. Repository-admin access alone is not enough. PullPing checks ownership again after you approve repository-name sharing.

Does PullPing change anything in GitHub?

No. PullPing receives GitHub events and can refresh PR snapshots through read-only API calls. Reviews, comments, and merges still happen in GitHub.

Are digests sent automatically?

Run /pullping digest for an immediate summary. Route admins can schedule daily UTC digests with /pullping digest schedule HH:MM. Use Manage reminder on a digest for weekdays, weekly or custom days, and time zones.

Can reviewers choose when to review?

Connect your GitHub identity with /pullping connect, then open Details on a PR where your review is requested. Choose a review time and optionally enable a private reminder. Authors can also set urgency and request a review response time.

How do we get started?

The invite-only pilot starts at $29 per Slack workspace each month. Approval and billing are manual. Ask your onboarding contact for an invite, then connect Slack and GitHub.

YOUR TEAM HAS BETTER THINGS TO DO.

Less “any updates?”
More good work.

Give your pull requests a little forward motion.

Request access A small addition to Slack. A calmer way to ship.