SUMMARIZATION
GitLab Release Tag to Customer Changelog on ReadMe
When a GitLab release tag is published, collects every MR merged since the previous tag, rewrites them into customer-facing changelog prose.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab release tag publishedGitLab
- ActionFetch MRs merged since previous tagGitLab
- LogicFilter out internal/chore/ci MRs
- ActionSynthesize grouped changelog prose with OpenAIOpenAI
- OutputPublish dated entry to ReadMe changelogReadMe
What it does
Turns a GitLab release tag into a polished, customer-readable changelog entry published to ReadMe — no manual copy-pasting from MR titles.
When to use it
Use it when you cut releases via Git tags and want every public release to land on your ReadMe docs site with consistent, human-friendly notes instead of raw commit messages.
How it works
- 1A new GitLab release tag (e.g. `v2.4.0`) fires the trigger.
- 2The flow queries GitLab for all MRs merged between the previous tag and this one, pulling titles, descriptions, and labels.
- 3A filter drops MRs labeled `internal`, `chore`, or `ci` so only customer-relevant changes survive.
- 4OpenAI groups the remaining MRs into Added / Improved / Fixed sections and rewrites each into a benefit-led sentence in your brand voice.
- 5The synthesized markdown is published as a new dated entry on your ReadMe changelog, tagged with the release version.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ReadMeAPI docs, changelog, auth.
- 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.