PERSONAL PRODUCTIVITY

Weekly decision digest from the Notion register to Slack

On a schedule, summarizes the past week's decisions from the Notion register into a clean digest and posts it to a leadership Slack channel so nobody misses what got decided.

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule (e.g. Monday 8am)
  • ActionQuery Notion register for last 7 daysNotionNotion
  • LogicStop if no decisions this week
  • ActionGroup and summarize with OpenAIOpenAI
  • OutputPost digest to leadership Slack channelSlack

What it does

Closes the loop on a decision register by broadcasting it. Once a week it queries the Notion decision database for everything logged in the last seven days, groups the entries by owner or theme, writes a readable summary, and posts it to a Slack channel. The register stays the source of truth; the digest keeps the whole team aware.

When to use it

Use it when decisions are being captured but not communicated — leadership wants a Monday-morning recap, or distributed teams need a single async heartbeat of what changed. Pair it with any capture workflow that writes to the same Notion register.

How it works

  1. 1A weekly schedule triggers the run (e.g. Monday 8am).
  2. 2The workflow queries the Notion register for entries created in the last seven days.
  3. 3A logic step ends quietly if there were no decisions that week.
  4. 4An OpenAI step groups and summarizes the decisions into a scannable digest with owners and links.
  5. 5The digest is posted to the designated Slack channel as a formatted message.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.