CONTENT CREATION

Weekly Merged-MR Digest to Notion and Slack

Every Friday, summarizes the week's merged GitLab MRs into a plain-English shipping digest, publishes it to a Notion changelog page, and drops the highlights in a Slack channel.

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerschedule
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule (Friday PM)
  • ActionQuery MRs merged in last 7 daysGitLabGitLab
  • LogicFilter out chore/dependency/CI-only MRs
  • ActionWrite themed weekly summary with LLMOpenAI
  • ActionAppend entry to Notion changelog pageNotionNotion
  • OutputPost highlights to Slack channelSlack

What it does

Produces a recurring "what shipped this week" digest without anyone compiling it manually. It scans GitLab for all MRs merged in the last seven days, distills them into a readable narrative grouped by theme, appends the entry to a running Notion changelog, and posts a short highlights message to Slack.

When to use it

For teams that ship continuously rather than on tagged releases and want a steady weekly cadence of internal visibility. Great for keeping non-engineering stakeholders informed of progress without release ceremony.

How it works

  1. 1A scheduled trigger runs every Friday afternoon.
  2. 2The flow queries GitLab for all MRs merged in the trailing 7-day window.
  3. 3A logic step filters out chore, dependency-bump, and CI-only MRs so the digest stays signal-rich.
  4. 4An LLM step writes a themed weekly summary with a one-line headline.
  5. 5The entry is appended to the running Notion changelog page.
  6. 6A condensed highlights message posts to the team Slack channel.

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.