CONTENT CREATION

GitLab merged MRs to polished Notion release notes

When a release tag lands in GitLab, collects every merge request since the last tag, rewrites the terse commit titles into customer-friendly release notes.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitLab release tag pushedGitLabGitLab
  • ActionFetch merge requests since previous tagGitLabGitLab
  • LogicFilter out chore/CI/dependency MRs
  • ActionRewrite and group changes into release notesOpenAI
  • OutputPublish notes as a new Notion pageNotionNotion

What it does

Turns the raw list of merge requests shipped in a GitLab release into a clean, customer-readable changelog and files it in your Notion release-notes database. Engineers keep writing terse MR titles; customers get a polished page.

When to use it

Use it when you cut releases by pushing a Git tag and want the human-facing notes written automatically instead of someone hand-curating a doc every sprint. Best for teams whose source of truth is GitLab and whose docs live in Notion.

How it works

  1. 1A new tag push to GitLab fires the trigger.
  2. 2The flow queries GitLab for all merge requests merged between the previous tag and this one.
  3. 3A filter drops chore, CI, and dependency-bump MRs so only customer-relevant changes remain.
  4. 4An LLM step groups the survivors into Added / Improved / Fixed buckets and rewrites each into a benefit-led sentence in your brand voice.
  5. 5The result is published as a titled Notion page under your Releases database, tagged with the version number.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.