SUMMARIZATION

Daily Slack Thread Digest to Notion

Each morning, summarizes the longest Slack threads from the past 24 hours into a single Notion digest page with extracted decisions and open questions.

CategorySummarization
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekday 8am schedule
  • ActionFetch recent threads + repliesSlack
  • LogicKeep threads above reply threshold
  • ActionSummarize decisions and open questionsOpenAI
  • OutputPublish dated digest pageNotionNotion

What it does

Scans your busy Slack channels once a day, finds threads that crossed a noise threshold (lots of replies or participants), and condenses each into a tight summary. It pulls out what was decided, what is still open, and who is on the hook, then publishes everything as one dated Notion page so the team starts the day with context instead of scroll-back.

When to use it

Use it when important discussion happens in long Slack threads that nobody outside the thread ever reads. Good for leads who manage several channels and want a single morning read covering decisions and unresolved questions across all of them.

How it works

  1. 1A scheduled trigger fires every weekday at 8am.
  2. 2Pull threads from the watched channels with their replies from the last 24 hours.
  3. 3Filter to only threads above the reply or participant threshold so trivial chatter is dropped.
  4. 4Summarize each qualifying thread with OpenAI, separating decisions, open questions, and owners.
  5. 5Create a dated digest page in Notion containing every thread summary with a link back to Slack.

Set it up

What you configure once, before turning it on.

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