Turn Merged Pull Requests Into a User-Facing Changelog
Keep users informed — when PRs labeled user-facing merge, AI drafts a friendly changelog entry and publishes it after a quick review.
- 1
Trigger on Merges
Add a
GitHub Triggernode on PR merge, filtered to auser-facinglabel. - 2
Draft the Entry
Add an
OpenAInode turning the PR title and description into a benefit-focused changelog line. - 3
Send for Approval
Add a
Slacknode posting the draft with an approve button. - 4
Publish the Changelog
On approval, add an
HTTP Requestnode posting the entry to your changelog tool or docs. - 5
Activate and Test
Activate the workflow and merge a test labeled PR. Confirm a clean draft appears for approval.
Frequently asked questions
Why not auto-publish?
A quick review keeps the tone right and filters internal details that shouldn't be public.
Can I batch entries into a release?
Collect approved entries and publish them together on release day for a cleaner narrative.
Verify Every Shoot's Footage Is Backed Up Before You Leave Set
A videographer's nightmare is discovering a corrupt card after the client's one-time event. Log each card's offload and verify redundant backups before leaving set.
n8nTelegramGoogle SheetsReplay Failed Webhooks From a Dead Letter Queue Automatically
Failed inbound webhooks silently drop events that never get processed. Capture failures into a dead letter queue and replay them automatically once the issue clears.
n8nSlackBlock Disposable Email Signups From Poisoning Your Trial Metrics
Disposable-email trial signups inflate your funnel and abuse free tiers. Detect throwaway domains at signup and route them for verification before they count as trials.
n8nSlack
Keep every recipe free
FlowRecipesHub is free and always will be. If a workflow saved you time, chip in what you like — it helps us keep the lights on and build the next batch of automations for everyone.
Secure checkout via Paddle · one-time, no account needed