SUMMARIZATION
On-Demand Slack TL;DR to Notion Decision Log
A /tldr slash command summarizes the current Slack thread into a decision and key points, appends a timestamped entry to a Notion decision-log database.
How it runs
The automated pipeline, trigger to output.
- Trigger/tldr slash command invoked on a threadSlack
- ActionFetch thread messages and participant listSlack
- ActionLLM summarizes into decision plus key pointsOpenAI
- ActionAppend entry to Notion decision-log databaseNotion
- OutputReply in-thread with the Notion page linkSlack
What it does
This is the on-demand companion to automatic thread digesting. Anyone in a channel runs a /tldr slash command on a thread, and the workflow summarizes it into a one-paragraph decision plus bulleted key points. Instead of creating tasks, it writes a permanent, searchable entry into a Notion decision-log database with the date, channel, participants, and a link back to the Slack thread.
When to use it
Use it when the goal is institutional memory rather than task tracking: leadership decisions, architecture choices, policy calls. Teams that ask "why did we decide this?" months later get a clean, queryable Notion record instead of scrolling Slack history.
How it works
- 1A user runs the /tldr slash command, which delivers the command payload and thread reference.
- 2The thread's parent and replies are pulled from Slack along with participant names.
- 3The LLM produces a decision summary and key points in structured form.
- 4A new page is appended to the Notion decision-log database with metadata fields populated.
- 5The workflow replies in-thread (visible to the invoker) with the Notion page link confirming the decision was logged.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.