SUMMARIZATION

GitLab Release to Notion Archive plus Discord Announcement

On a release tag, synthesizes changelog notes once, archives the full version in a Notion release database, and posts a trimmed announcement to Discord.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitLab release tag publishedGitLabGitLab
  • ActionCollect MRs merged since previous tagGitLabGitLab
  • ActionGenerate detailed notes + short blurb with OpenAIOpenAI
  • ActionArchive full release in Notion databaseNotionNotion
  • OutputAnnounce trimmed blurb to DiscordDiscordDiscord

What it does

Generates release notes one time and fans them out two ways: a complete, searchable record in Notion and a short hype-friendly announcement in Discord.

When to use it

Use it when you need an internal source-of-truth release log (for support and sales) plus a punchy public announcement, and you don't want the two to drift apart.

How it works

  1. 1A GitLab release tag publish triggers the flow.
  2. 2The flow collects all MRs merged since the previous tag with their labels and authors.
  3. 3OpenAI produces two artifacts in one pass: a detailed structured changelog and a 2-3 sentence announcement blurb.
  4. 4The detailed changelog is written as a new page in a Notion release database, with version, date, and author properties set.
  5. 5The short blurb is posted to a Discord announcements channel with a link reference to the version.

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 DiscordCommunity channels + voice + bots.
  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.