Generate Verified Release Notes from Notion Databases
How to query Notion project databases, filter by Status and completion dates, and generate accurate weekly changelogs.
Soobrief Team — Product & Engineering, Sooapps ·
In short
Generating a verified changelog from Notion requires querying a database with an explicit `Status == 'Done'` filter and a dedicated `Completed Date` property. Mapping database relation rollups to product areas ensures clean, repeatable release documentation without manual page copying.
Generating a verified changelog from Notion requires querying a database with an explicit Status == 'Done' filter and a dedicated Completed Date property. Mapping database relation rollups to product areas ensures clean, repeatable release documentation without manual page copying.
Many modern tech companies use Notion as their all-in-one product management hub. But pulling release notes out of Notion databases usually involves tedious manual filtering and copy-pasting across pages.
1. Database Schema Requirements for Automation
To generate reliable changelogs from Notion, your database must include:
- Status Property: Type
status with a group matching "Complete".
- Completed Date Property: Type
date, populated automatically via Notion database automations or manually on task completion.
- Category / Area: Type
select or relation indicating the target product area.
{
"filter": {
"and": [
{
"property": "Status",
"status": { "equals": "Done" }
},
{
"property": "Completed Date",
"date": { "on_or_after": "2026-09-03" }
}
]
}
}
2. Ingesting Page Content Safely
While the task title provides the changelog item, Notion page bodies often contain extensive mockups, meeting notes, and internal discussions. The ingestion layer selectively extracts only the top summary callout, ensuring internal draft notes are never leaked to customer release feeds.