Dev Ops · n8n

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.

difficulty Intermediatesetup 35 minresult Shipped features become clear, user-friendly changelog entries automatically, closing the loop with customers.
  1. 1

    Trigger on Merges

    Add a GitHub Trigger node on PR merge, filtered to a user-facing label.

  2. 2

    Draft the Entry

    Add an OpenAI node turning the PR title and description into a benefit-focused changelog line.

  3. 3

    Send for Approval

    Add a Slack node posting the draft with an approve button.

  4. 4

    Publish the Changelog

    On approval, add an HTTP Request node posting the entry to your changelog tool or docs.

  5. 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.

About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.