Slack Notifications

Get notified in Slack the moment SiftPulse acts — stale-PR nudges, ready-to-merge PRs, re-review blockers, and high-priority issues — using a standard incoming webhook URL. No OAuth, no app review waiting period.

How it works

You supply a Slack incoming webhook URL. SiftPulse posts a formatted Block Kit message to that URL whenever a configured event fires. Messages include the PR/issue title, repo name, and a direct link back to GitHub — so you can act without touching the SiftPulse dashboard.

Setup — 3 steps

Step 1

Create a Slack incoming webhook

Go to api.slack.com/apps and click Create New App → From scratch.
Name it anything (e.g. "SiftPulse") and pick your workspace.
Under Features → Incoming Webhooks, toggle it On.
Click Add New Webhook to Workspace, pick a channel, and authorize.
Copy the Webhook URL — it starts with https://hooks.slack.com/services/…

Already have a webhook from another app? You can reuse it — incoming webhooks are per-channel, not per-app.

Step 2

Paste it in your SiftPulse dashboard

Go to your dashboard → scroll to 💬 Slack notifications. Paste the webhook URL and click Save Slack settings.

Hit Test webhook to fire a sample message — you should see it in Slack within a few seconds.

Step 3

Choose which events to receive

Toggle any of the 4 event types on or off from the same settings panel. All are on by default.

Notification events

🐢

Stale-PR nudge posted

Fires when SiftPulse comments on a stale PR (author stuck, reviewer stuck, or long-running). Includes PR title, repo, nudge type, and a direct link to the PR.

🚦

PR ready to merge

Fires when a PR's readiness state transitions from not-ready to ready. Triggered by CI passing, approvals granted, or conflicts resolved — and SiftPulse's readiness comment updates to green.

🔄

Re-review finds new blockers

After a new commit is pushed to an open PR, SiftPulse re-reviews the incremental diff. This notification fires only when the re-review surfaces at least one new blocker — not on every push.

🎯

High-priority issue triaged

Fires when SiftPulse triages a new issue and rates it HIGH or CRITICAL priority. Includes suggested owner logins so you can assign it immediately.

Reliability

Retry behavior: on a 5xx response from Slack, SiftPulse retries up to 2 more times with a 2-second back-off between attempts. On a 4xx (webhook revoked or deleted), the webhook is auto-disabled and you'll see the error in the dashboard settings panel — paste a new URL to re-enable. Every send attempt is logged internally.

Notifications are sent asynchronously — they never delay the main PR review or triage flow. A Slack outage will not affect your GitHub comments.

Migrating to a native Slack app

Incoming webhooks cover the 80% case instantly with zero OAuth review wait time. When Slack approves a full OAuth integration, we'll let you upgrade with a one-click "Connect via Slack" button — your existing notification preferences will carry over automatically.

Ready to set it up?

Takes less than 2 minutes.

Go to Dashboard →