SUMMARIZATION
Fan Out All-Hands Recaps to Per-Team Slack Channels
After a Zoom all-hands, generate one recap per Slack channel audience and post each tailored version into the matching team channel with a thread for follow-up questions.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom all-hands recording completedZoom
- ActionFetch recording transcriptZoom
- ActionGenerate per-channel recap variantsOpenAI
- LogicMap each variant to its Slack channel
- OutputPost recap to each team channel with follow-up threadSlack
What it does
Posts department-specific summaries of an all-hands meeting into the right Slack channels, so each team sees the parts that matter to them without scrubbing a full recording.
When to use it
Your team lives in Slack and nobody rewatches recordings. You want #eng, #sales, #cs, and #company-wide to each get a recap written for that audience, automatically, minutes after the call ends.
How it works
- 1A Zoom recording-completed event triggers for the all-hands.
- 2Fetch the transcript from Zoom.
- 3OpenAI generates a channel map: one concise recap per configured audience plus shared headline bullets and decisions.
- 4A logic step matches each generated variant to its destination Slack channel ID.
- 5Post each variant to its channel as a formatted message, then open a thread reply inviting questions and linking the recording so discussion stays in one place.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.