Where honk hears things
Pull requests, reviews and checks from GitHub today. Anything that can send a webhook next.
GitHub → Slack today. Everything else, patched in.
Quiet until it matters. Then: honk.
honk watches your GitHub and pings you in Slack only when something is actually waiting on you. Patch together what it listens to, when it should care and who it honks at. Then forget it’s there.
honkAPP · 09:41
Honk! PR #482 “Fix token refresh” has been waiting on your review for 2 days.
Try it · nothing gets sent
Patch it together.
Pick what honk listens to, when it should care and who it honks at. Plugs that don’t fit won’t go in, and honk tells you why.
ListenGitHub
Review requested
pull_request
Live
Only ifFilter
Still waiting
no response after 24h
checking
Honk atSlack
DM the reviewer
@{reviewer}
Ready
Plugged in
honk will listen for “Review requested” on GitHub, only if still waiting, and honk at Slack (@{reviewer}).
What lands in Slack
honkDIRECT MESSAGE
Honk! PR #482 “Fix token refresh” is waiting on your review, and has been for 26 hours.
Three jacks. No spaghetti.
The bouncer
Age, labels, branches, quiet hours. Chain as many as you like. Most noise never makes it past here.
Where the noise goes
A Slack DM or a channel today. Email digests, Discord and Teams are on the way.
Round plugs into diamonds, diamonds into squares. Squares don’t plug into anything: once honk has honked, it’s done. If a combination makes no sense, the jack simply won’t take the cable.
Fewer, better honks.
A notification tool that notifies you less. That’s the whole idea.
One honk per thing
If it’s still waiting tomorrow, honk nudges you again. Politely, once.
Snooze from Slack
Hit Snooze 1h right on the message. honk remembers and honks again later.
Quiet hours
Nothing honks at 2am unless you’ve said it’s allowed to.
Put a goose on your shoulder.
Connect GitHub and Slack, plug in your first flow, then get back to work.