ENGINEERING

Weekly digest of merged PRs to Notion and Slack

Once a week, collects everything merged into main over the past seven days, has AI write a readable shipped-this-week summary, saves it as a Notion page.

CategoryEngineering
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionList PRs merged to main this weekGitHubGitHub
  • ActionSummarize shipped work with AIOpenAI
  • ActionSave digest as Notion pageNotionNotion
  • OutputPost highlights to SlackSlack

What it does

Every week the workflow pulls all pull requests merged into your main branch over the last seven days, then uses an AI model to write a digest of what shipped, grouped by theme and written for a mixed audience of engineers and stakeholders. It archives the full digest as a dated Notion page and posts a short version with the key highlights to Slack.

When to use it

When leadership or adjacent teams keep asking what engineering shipped this week and you want a repeatable, low-effort answer. Good for teams that merge to a single main branch and want a running history of progress.

How it works

  1. 1A weekly schedule (for example, Friday afternoon) starts the run.
  2. 2The workflow lists PRs merged into main in the last seven days via GitHub.
  3. 3An AI model summarizes them into a themed shipped-this-week narrative.
  4. 4It creates a dated page in a Notion database with the full write-up.
  5. 5It posts a condensed highlights message to Slack with a link to the Notion page.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  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.