Honk
GitHub-to-Slack notifications with built in filtering
Start new thread
Dragos Dumitrache

Honk - GitHub-to-Slack notifications with built in filtering

by•
GitHub's built-in Slack integration is all-or-nothing. The third-party tools charge $10-15/user/month for what is fundamentally a webhook router. We thought engineering teams deserved better. Honk gives you smart, rule-based GitHub notifications in Slack — with flat per-org pricing that doesn't punish you for growing your team.

Add a comment

Replies

Best
Dragos Dumitrache
Maker
📌
**Key Features:** 🎯 **Composable Filter Rules** — Build rules with real logic: filter by repo, branch, author, labels, reviewers, or PR state. "Urgent PRs in main" OR "any PR where I'm a reviewer" — not just repo-to-channel mapping. 💬 **Auto-Mentions** — Automatically @mention PR authors, reviewers, and assignees. No manual user mapping table to maintain — resolved automatically via email. 🧵 **Threaded Updates** — Reviews, comments, and CI results thread under the original PR notification. Your channels stay readable. 📊 **Metrics Dashboard** — Cycle time, time to first review, CI health, PR size trends, and a reviewer leaderboard. Because you're already processing the data — why not surface it? 💰 **Flat Pricing** — Per org, not per seat. Free tier for small setups. Paid plans don't change price when you hire. 🔍 **Review Notifications** — Configurable per rule. Filter by review state. Separate auto-mention config for reviews. No more "LGTM" spam. **Launch Offer:** 3 months free on any paid plan — use code `GETHONK` at checkout. **Pricing (after trial):** - Free: 1 Slack channel, PR events - Starter ($100/mo): 5 channels, all events, metrics dashboard - Team ($200/mo): Unlimited channels, priority support **First Comment:** Hey Product Hunt! I'm Dragos. I built Honk because I was frustrated with the GitHub-Slack notification landscape. GitHub's built-in integration has no filtering. The paid tools work, but per-seat pricing for a notification router never sat right with me — the infrastructure cost doesn't scale with headcount, so why should the price? I also just wanted to build something. I'm a staff engineer by day, and side projects are how I stay connected to the full stack — from data modeling to billing integration to frontend polish. Honk started as a weekend itch-scratch and grew into something I'm genuinely proud of. The metrics dashboard was pure scope creep. Once I had all the webhook data flowing through, I couldn't resist building cycle time charts and reviewer leaderboards. Turns out "time to first review" is the single most actionable metric for engineering teams — it correlates directly with developer frustration and PR cycle time. **I'm offering 3 months free to early adopters** — use the coupon code `GETHONK` at checkout. I'm still early and I want real teams using this so I can learn what actually matters. Fair warning: it's a young product and things might not work perfectly yet. If you hit a rough edge — and you probably will — reach out at dragos@gethonk.io and I'll get it sorted out. No support queue, just me fixing things quickly because I care about this working well. Whether it's bugs, feedback, or feature requests, I want to hear it all.