Draft Customer Changelogs from GitHub PRs to Gmail (n8n)

Draft customer changelogs from merged GitHub PRs—directly into a Gmail draft

This n8n workflow automatically reviews your merged GitHub pull requests, filters out internal/bot changes, asks an OpenAI-compatible model what customers would actually notice, and then generates a customer-facing changelog as a Gmail draft. Nothing is sent—your team stays in control.

What this workflow does

• Runs on schedule (or on demand): Executes every Friday by default, loading configuration such as repositories, the time window, and the email recipient.
• Pulls recently merged PRs: Fetches recently closed GitHub issues and keeps only pull requests that were merged within your configured window.
• Filters internal noise: Removes bot-authored changes and excludes PRs marked as internal via conventional-commit prefixes or skip labels.
• Prevents duplicate evaluations: Checks the n8n Data Table shipped_changes to skip PRs already judged in prior runs, and caps the remaining list to a maximum count.
• Decides what customers notice: Sends the remaining PR titles and descriptions to an OpenAI-compatible chat model to determine which changes a customer would notice.
• Creates a customer changelog: Groups results into Added, Fixed, and Changed, then creates a Gmail draft including a short summary and the full list of judged PRs.
• Records what was shipped: Upserts one record per judged pull request into shipped_changes so future runs don’t re-evaluate.

Use cases

• SaaS teams that want weekly, customer-friendly release notes without manual PR triage.
• Automation engineers who need an n8n workflow to transform GitHub activity into marketing-ready updates.
• Operators who prefer reviewable outputs via Gmail drafts rather than auto-sending.

Technical details

• Integrations / nodes: github, gmail, plus logic nodes such as if, set, code, and no op.
• Data storage: n8n Data Table shipped_changes with columns including pr_key, repo, number, and title.
• Modeling: Uses an OpenAI-compatible chat model to select customer-noticeable changes.

Ideal for n8n automation workflows that bridge GitHub releases and customer communications—without sending emails automatically.