A Notion changelog template that turns commits into release notes
This gives you a Changelog database, a prompt that rewrites a week of commits or tickets into plain release notes, and a checklist for updates that could break something for users. A dated list of changes is the plainest evidence that a small product is still looked after.
Inside the n8n workflow in the download
Notion: get Ready entries Sticky note
Every node is explained below, with the matching Notion database schema, property by property.
Free. One email with the files, then occasional updates. Unsubscribe any time.
- Setup: 45 to 60 minutes
- n8n + Notion
- Uses standard n8n nodes that work on n8n Cloud and self-hosted.
How it works under the hood, node by node
- Notion: get Ready entries: Pulls changelog entries whose Status is Ready.
- Sticky note: Connect your email tool here to send the notes, then mark the entry Published.
| Property | Type | Notes |
|---|---|---|
| Title | Title | What changed, in the user's words |
| Version | Text | e.g. 1.4.0 |
| Audience notes | Text | Who this affects and what they need to do |
| Breaking? | Checkbox | Triggers the breaking-change checklist |
| Status | Select | Draft, Ready, Published |
| Ship date | Date |
Also in the download
- A 'commits to notes' Claude prompt: paste your commit log or closed tickets, get user-facing notes grouped into new, improved and fixed
- A breaking-change checklist: what to warn users about, and when
- An email stub for announcing each release to your list
Set it up
- Create the Changelog database with the properties above.
- Once a week, paste your commits or closed tickets into the prompt.
- Save the output as a Draft entry, edit it, and set it to Ready.
- Optional: import the workflow and connect your email tool to send Ready entries.
- Publish the entry on your site's changelog page and mark it Published.
Stuck on the import? Importing an n8n workflow and setting up the Notion database cover the common snags.
Questions
Why a changelog at all for a small product?
It shows buyers and prospects the product is maintained. It also gives you a record for support: when someone reports a bug, you can see whether it was fixed and in which version.
Is the workflow required?
No. The database and prompt are the core. The workflow only automates sending Ready notes to your email list.
What counts as breaking?
Anything that makes a user change something on their side: a renamed field, a removed option, a new required step. Tick Breaking? and follow the checklist.
Updated