SUMMARIZATION
Weekly Slack Channel Decision Digest to Linear
On a weekly schedule, scans a Slack channel's threads from the past 7 days, extracts every decision and unowned action item.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule (e.g. Monday 8am)
- ActionFetch channel threads from the past 7 daysSlack
- ActionLLM clusters threads into decisions with action itemsOpenAI
- LogicFilter out action items that already have a tracked task
- ActionCreate Linear issues for untracked action itemsLinear
- OutputPost consolidated weekly decision digest to channelSlack
What it does
Decisions made across a busy week scatter through many threads and never get a single review. On a weekly cadence this workflow pulls the channel's threaded conversations from the last seven days, asks the LLM to extract each distinct decision and its action items, and assembles one digest. It then opens Linear issues for action items that don't already have a corresponding tracked task, so nothing agreed-upon falls through the cracks.
When to use it
Use it for a leadership or squad channel where you want a Monday-morning recap of what was decided and what still needs an owner. It complements per-thread extractors by catching decisions nobody explicitly closed out.
How it works
- 1A weekly schedule fires the trigger (for example Monday 8am).
- 2The channel's threaded messages from the past 7 days are fetched from Slack.
- 3The LLM clusters the threads into distinct decisions, each with action items and owners.
- 4A filter separates action items that already reference a tracked task from those that don't.
- 5New Linear issues are created for the untracked action items.
- 6A consolidated weekly digest, listing decisions and links to new issues, is posted to the channel.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.