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.
- 1
Receive the release
Add a
Webhooknode and register it in GitHub for thereleaseevent. AFilterkeeps onlyaction == 'published'and non-prerelease tags so drafts and betas don't fire announcements. - 2
Rewrite with Claude
An
HTTP Requestto Claude sends the release name, tag and body, asking for a friendly changelog in three sections — New, Improved, Fixed — that skips internal-only changes and speaks to end users. Ask for markdown so it renders in both Slack and Discord. - 3
Post to Slack
A
Slacknode posts the changelog to your team channel with a header like🚀 v{{tag}} is live. This keeps everyone — support, sales, docs — aware the moment a version ships. - 4
Post to Discord
An
HTTP Requestto your Discord channel webhook posts the same changelog to your community. Users see what changed without hunting the releases page, which reduces 'is X fixed yet?' questions. - 5
Archive the changelog
A
Google Sheets(or Notion) node appends the version, date and the polished changelog text. Over time you accumulate a clean, human-readable release history you can publish or reuse anywhere.
Frequently asked questions
How is this different from GitHub's auto-generated notes?
GitHub's auto notes are a raw list of merged PR titles — great for developers, opaque for users. This workflow has Claude group those changes into 'New', 'Improved' and 'Fixed' sections written in plain language, dropping internal refactors users don't care about. It's the difference between a commit log and a real changelog.
Does it announce pre-releases too?
Only if you want it to. The release payload includes a `prerelease` flag; the workflow filters it out by default so beta tags don't spam your community. Flip the filter to include pre-releases if you run a public beta channel.
Can I also post to X or a blog?
Yes — the AI output is plain text, so you can branch to any destination. Add an HTTP Request to X's API for a short 'we just shipped' post, or append the changelog to a Google Doc/CMS. Slack and Discord are the defaults because that's where teams and communities actually read release news.
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
Auto-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.
Free recipePost 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.