Draft customer-facing changelogs from merged GitHub PRs with OpenAI and Gmail
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (11)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - GitHub
n8n-nodes-base.github - Data table
n8n-nodes-base.dataTable - If
n8n-nodes-base.if - Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Gmail
n8n-nodes-base.gmail - No Operation, do nothing
n8n-nodes-base.noOp
What it does
Quick overview Reads merged pull requests from your repositories, drops the bots and the changes nobody outside the team can see, asks a model which of the rest a customer would notice, and drafts the changelog as a Gmail draft. Nothing is sent. How it works 1. Runs every Friday on a schedule (or on demand) and loads configuration such as repositories, time window, and email recipient. 2. Fetches recently closed GitHub issues for each repository and keeps only pull requests that were actually merged within the configured window. 3. Removes bot-authored changes and PRs marked as internal via conventional-commit prefixes or skip labels. 4. Checks the n8n Data Table to skip pull requests that have already been judged in previous runs and caps the remaining list to a maximum count. 5. Sends the remaining PR titles and descriptions to an OpenAI-compatible chat model to decide which changes a customer would notice. 6. Uses the model to write a customer-facing changelog grouped into Added, Fixed, and Changed, then creates a Gmail draft with the changelog, a short summary, and a full list of judged PRs. 7. Upserts one record per judged pull request into the n8n Data Table so future runs do not re-evaluate the same changes. Setup 1. Add a GitHub credential with access to the target repositories and update the repository list in Settings (as comma-separated owner/name values). 2. Create an n8n Data Table named shippedchanges with columns prkey, repo, number, title, verdict, and mergedon. 3. Add an OpenAI-compatible credential for the chat model node and choose a model that can handle the configured maxchanges prompt size. 4. Add a Gmail credential and set the recipient address in Settings (emailto) for where the draft is addressed. Requirements - A GitHub credential that can read the repositories you list, a Gmail credential for the draft, and any OpenAI-compatible key. Customization - skipprefixes and skiplabels in Settings decide what counts as invisible before a model ever sees it. maxchanges caps how many go into one prompt - a longer list is an answer long enough to be cut off.