Post a Daily GitHub Dev Standup Digest to Slack
An n8n workflow that gathers yesterday's merged pull requests, opened issues and commits across your repositories each morning, has Claude summarize them into a readable standup, and posts it to Slack — so your async team knows exactly what shipped without a live meeting.
- 1
Schedule the morning run
Add a
Schedule Triggerset to weekday mornings at hour9. Running Monday–Friday avoids weekend noise; adjust if your team ships on weekends. - 2
Query merged PRs and new issues
Two
HTTP Requestnodes hithttps://api.github.com/search/issueswith queriesis:pr is:merged merged:>={{yesterday}} org:YOUR_ORGandis:issue created:>={{yesterday}} org:YOUR_ORG. Use{{$today.minus({days:1}).toFormat('yyyy-MM-dd')}}for the date. - 3
Combine the activity
A
Merge(orCode) node stitches the PR and issue results into one payload with titles, authors and links, plus totals. This is the raw material for the summary. - 4
Summarize with Claude
An
HTTP Requestto Claude turns the combined activity into a grouped standup: a headline count line, 'Shipped' highlights, 'In progress / new issues', and any flagged risks. Ask for concise markdown suitable for Slack. - 5
Post to Slack
A
Slacknode posts the digest to your engineering channel with a dated header. The team scrolls it with coffee and starts the day aligned — no meeting required.
Frequently asked questions
Does this replace standup meetings?
For distributed teams, often yes — a daily written digest of what actually merged and moved gives everyone the shared context standups aim for, without the timezone pain. Many teams keep a short weekly sync for blockers and use this digest to cover the 'what did you do' part every day.
How does it pull activity across multiple repos?
It uses GitHub's Search API (`/search/issues`) with date-qualified queries like `is:pr is:merged merged:>=YESTERDAY org:yourorg`. One query per activity type covers your whole org. For a handful of repos you can scope by `repo:` instead of `org:`.
Won't a busy day produce a huge message?
That's why Claude summarizes rather than dumping raw lists. The prompt asks for grouped highlights — themes, notable PRs, anything risky — capped to a readable length, with a count line ('12 PRs merged, 5 issues opened'). Detail lovers still get a link to the full activity.
Escalate GitHub Security Alerts to PagerDuty Instantly
An n8n workflow that catches GitHub Dependabot and code-scanning security alerts, filters for high and critical severity, and opens a PagerDuty incident with the vulnerability details — so a serious CVE in your dependencies wakes the on-call engineer instead of sitting unseen in the Security tab.
Free recipe
Turn a New GitHub Release into a Plain-English Changelog Announcement
An n8n workflow that fires when you publish a GitHub release, has Claude rewrite the raw release notes into a friendly, user-facing changelog, and posts it to Slack and a Discord community channel — so shipping a version instantly tells your users what's new, in words they understand.
Free recipeAuto-Triage New GitHub Issues with AI Labels and Priority
An n8n workflow that fires on every new GitHub issue, uses Claude to classify it by type, priority and affected area, then applies the right labels and posts a triage summary to Slack — so your backlog stays organized without a maintainer manually sorting each report.