SUMMARIZATION
Daily AI Digest of a Busy Slack Channel
Each morning, pull the last 24 hours of messages from a high-traffic Slack channel, distill them with GPT into a themed digest, and post it back as a clean recap.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires at 8:00 AM
- ActionFetch last 24h of channel messages + threadsSlack
- LogicSummarize into themed digest with GPTOpenAI
- OutputPost recap back to Slack channelSlack
What it does
This workflow turns a noisy, fast-moving Slack channel into a single digestible recap delivered every morning. On a schedule, it fetches the previous 24 hours of messages from a chosen channel, sends the raw thread to OpenAI with a summarization prompt, and posts the result back into Slack as a structured digest — grouped by theme (decisions made, open questions, action items, links shared) with the key contributors credited. Nobody has to scroll back through 300 messages to find out what they missed.
When to use it
Reach for this when a channel like `#engineering`, `#incidents`, `#customer-feedback`, or `#general` generates more chatter than any one person can track. It's ideal for distributed teams across time zones (catch up on what happened overnight), managers who need signal without sitting in every thread, and anyone returning from PTO. Run it once a day for a steady pulse, or bump the schedule to twice daily for very active channels.
How it works
A scheduled trigger fires each morning (default 8:00 AM in your workspace timezone). The workflow calls the Slack API to read all messages posted to the target channel since the last run, including thread replies, and normalizes them into a single transcript with usernames and timestamps. That transcript is passed to OpenAI with a prompt that instructs the model to extract decisions, action items, unresolved questions, and notable links — and to flag anything urgent. The model returns formatted Slack markdown, which the final step posts straight back into the channel (or a dedicated `#daily-digest` channel) so the recap lives where the team already works. If the channel was quiet, it posts a short "nothing major today" note instead of an empty summary.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect OpenAIModels, embeddings, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
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…
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.
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.
Escalate blockers from Loom standups to Slack
Transcribes each new Loom standup video, uses AI to detect blockers and dependencies.
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.