Notifications · Slack, Teams & Email

The Friday-morning recap your CTO actually reads.

Invisible products get cancelled. RepoWarden posts a weekly (or daily) digest into Slack or Teams so the work shows up where the buyer already lives — not buried in an email folder, not sat on a dashboard nobody opens.

01Anatomy

One scannable message

Header, two-line summary, time-saved estimate, security-first highlights, looming runtime warnings, and actions. The whole thing is the size of a Slack notification preview — readable in two seconds without expanding.

🛡️ RepoWarden weekly digest — Apr 24–30
Acme Eng · 4 PRs merged · 2 CVEs patched · 3 dep updates · 1 CI fix · 1 needing review
Time saved
~4h
Estimated value
~$300
Highlights
🔒 Patched CVE-2024-39338 (axios SSRF, CVSS 9.1)
acme/api · merged in 6h
📦 Bumped Next.js 14.2 → 15.0
acme/web
🛠 Fixed flaky CI on workspace lockfile drift
⚠️ Node 18 EoL in 47 days
View full reportSnooze 1 week
02Channels

Three places, one schedule

Slack

Block Kit message with linked highlights and action buttons. Setup is one Incoming Webhook URL — no app to install, no OAuth flow to walk an admin through.

Slack setup →

Microsoft Teams

Adaptive Card 1.4 posted via a Teams Workflow webhook (the supported path post-2025 connector deprecation). Same content, same actions.

Teams setup →

Email

On by default — a Monday weekly report goes to opted-in members. Add a custom email-channel digest if you want a different time or daily cadence.

Email digest →
03Why it matters

Visibility is the strongest churn-prevention you can buy

For the buyer

CTOs and Heads of Engineering don't read PR diffs. They renew tools they can see working. The digest lands in #engineering at 9am every Friday with hard numbers — PRs merged, CVEs patched, time saved, value in dollars.

For the team

One shared touchpoint replaces "did we merge that Renovate PR?" Slack threads. Highlights link to the PR. Issues that still need human review are surfaced so they don't sit forever.

No noise weeks

Quiet windows with zero merged PRs and nothing in review get skipped — sending "nothing happened" trains people to mute the channel, and a muted channel is worse than no channel.

Snooze, don't unsubscribe

One-click snooze for a week from the message. Members can snooze; only owners and admins can edit or delete a schedule. Holiday weeks don't pollute the channel and don't lose the whole setup.

04Configuration

Configurable per channel

Frequency

Weekly (default) or daily. Each schedule is independent — you can run a daily Slack digest for security and a weekly email digest for the wider team.

Local time

Pick day-of-week and hour-of-day in any IANA timezone. Defaults to Friday 9am, in your team's timezone.

Scope

All repos on the team, or a specific list. Lets you route #frontend digests to one channel and #platform digests to another.

Multiple per team

Add as many digests as you need. Each has its own snooze state — silencing one doesn't silence the others.

Retries

3 attempts with exponential backoff on transient 5xx and 429 responses. 4xx short-circuits so a bad URL fails fast and you can fix it.

Roles

Owners and admins create / edit / delete schedules. Any member can snooze.

Ship it

Two minutes, then your CTO sees everything you ship

Available on every plan. Setup is one webhook URL — no OAuth flow, no admin approval, no SAML config.