GitHub to Slack
A Node webhook service that groups GitHub issue-close events with their closing comments into a single Slack notification, replacing Slack's noisy default GitHub integration; deployable to Heroku.
- BPM
- 180
- GRADE
- B
- LEVEL
- 8
- RELEASES
- 1
- YEARS
- 2015–2015
Too Much Data
I wrote the complaint down when I was annoyed: "Slacks current integration sends too much data that I typicaly do not need." Typo included. That's how this project started.
What I wanted was one notification when an issue closed, with the comment that closed it, instead of a channel full of every event GitHub sends. So in May 2015 I wrote a Node webhook service that sat between the two, grouped the close and its comments together, and forwarded a single message. You configured it with environment variables: the Slack webhook URL, an optional channel override, a bot username, an icon URL or emoji, and SLACK_AUTHOR_NAMETYPE, which made an extra call to GitHub so it could say Devin instead of arzynik. There was a Heroku deploy button too.
I worked on it from May to October and tagged v0.2.0 at the end. I used it every day. The setup instructions were nine steps, including which GitHub events to check, and I mostly wrote them for future me.
led to
- Tracker2026GitHub events piped to chat