SUMMARIZATION
Zoom Webinar to ReadMe Article with Slack Approval Gate
Drafts a chaptered ReadMe how-to from a Zoom webinar, then posts the TL;DR to Slack for a human approve/reject decision before the article is published live.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom recording completedZoom
- ActionChapters + TL;DR from transcriptOpenAI
- ActionCreate ReadMe draftReadMe
- ActionPost TL;DR to Slack for approvalSlack
- LogicBranch on approve / reject
- OutputPublish on approve, notify threadReadMe
What it does
Same chaptering and TL;DR generation as the core webinar-to-docs flow, but with a human-in-the-loop gate. After the draft is built it posts the proposed title and TL;DR to a Slack channel with approve/reject actions. Only on approval does it flip the ReadMe page from draft to published; on rejection it leaves the draft and notes who declined.
When to use it
Use it when AI-generated docs must not go live unreviewed — regulated products, customer-facing knowledge bases, or any team that wants editorial sign-off without leaving Slack.
How it works
- 1A Zoom recording-completed event fires.
- 2The transcript is fetched and sent to OpenAI to produce chapters with timestamps and a TL;DR.
- 3The article is created as a ReadMe draft.
- 4A Slack message posts the title and TL;DR with Approve and Reject buttons.
- 5A branch waits on the response: approve publishes the ReadMe draft live; reject keeps it as a draft.
- 6The outcome and reviewer are posted back to the Slack thread.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ReadMeAPI docs, changelog, auth.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.