CONTENT CREATION

Release-Tag Changelog to Notion Draft + Slack Approval

When a GitLab release tag is published, drafts structured release notes from the merged MRs in that milestone, saves them as a Notion draft.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitLab release tag publishedGitLabGitLab
  • ActionFetch MRs merged since previous tagGitLabGitLab
  • ActionDraft & categorize release notes with LLMOpenAI
  • ActionWrite draft to Notion releases databaseNotionNotion
  • OutputPost Slack approval card with draft linkSlack

What it does

Turns a freshly tagged GitLab release into a clean, human-readable changelog and parks it for review. It collects every merged MR since the previous tag, groups them into Added / Fixed / Changed buckets, writes a draft release-notes page in Notion, and pings your team in Slack for sign-off.

When to use it

For teams that cut versioned releases on GitLab and want consistent changelogs without writing them by hand — but who don't want auto-publishing. The Slack approval gate keeps a human in the loop before customer-facing copy ships.

How it works

  1. 1A GitLab release-tag event fires the workflow with the new tag name.
  2. 2The flow fetches all MRs merged between the previous tag and this one, reading titles, labels, and descriptions.
  3. 3An LLM step categorizes each change and drafts release notes in your house voice.
  4. 4The draft is written to a Notion page in a "Pending Releases" database.
  5. 5A Slack message posts the summary plus a link to the Notion draft for approval.

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
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.