SUMMARIZATION
Release-tag changelog: distill merged PRs into a Notion changelog page
When you publish a GitHub release, this collects every PR merged since the previous tag, summarizes them into stakeholder-friendly notes grouped by type.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub release publishedGitHub
- ActionList PRs merged since previous tagGitHub
- ActionSummarize and group PRs into changelog entriesOpenAI
- LogicFilter out chore/dependency-only PRs
- OutputCreate grouped changelog page in NotionNotion
What it does
Turns a raw GitHub release into a polished, human-readable changelog. On publish, it diffs the new tag against the previous one, pulls in the merged PRs, and uses an LLM to write plain-English entries grouped into Features, Fixes, and Internal — then publishes a clean page in your Notion changelog database.
When to use it
For teams that cut tagged releases and want a non-engineer-friendly changelog without hand-writing it every time. Ideal when product, support, and leadership all read Notion and shouldn't have to parse commit logs.
How it works
- 1A GitHub release-published event fires the workflow with the new tag.
- 2The flow fetches the previous tag and lists all PRs merged in that range, including titles, labels, and bodies.
- 3An OpenAI step rewrites each PR into a concise changelog line and sorts it into Features / Fixes / Internal by label and content.
- 4A logic step drops noise (dependency bumps, chore-only PRs) so stakeholders see signal.
- 5A new Notion page is created in the changelog database with the version, date, and grouped sections.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.