SUMMARIZATION
Auto-chapter new Loom demos into a searchable Coda transcript index
When a new Loom video lands in your demo library, this fetches the transcript, generates timestamped chapters and a summary with OpenAI.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom video processed in demo workspaceLoom
- ActionFetch transcript + video metadata from LoomLoom
- ActionGenerate chapters, titles, and summary with OpenAIOpenAI
- ActionUpsert searchable row into Coda index tableCoda
- OutputWrite deep-linked chapter URLs back to the rowCoda
What it does
Every new product-demo recording posted to your Loom workspace is automatically broken into timestamped chapters, summarized, and filed as a searchable row in a Coda table. Your team stops scrubbing through 20-minute videos and starts searching transcripts by feature name.
When to use it
Use this when your sales, success, or product teams record demos in Loom and nobody can find the one clip that shows a specific feature. It turns a pile of unlabeled videos into a queryable knowledge base.
How it works
- 1A Loom webhook fires when a video finishes processing in the demo workspace.
- 2The flow pulls the full transcript and metadata (title, duration, owner, share URL) from the Loom API.
- 3OpenAI segments the transcript into logical chapters with start timestamps, writes a one-line title per chapter, and produces a 2-sentence overall summary.
- 4A Coda action upserts a row keyed on the Loom video ID, storing the summary, chapter list, full transcript text, and deep-link timestamps so any term is searchable.
- 5The deep-linked chapter URLs are written back as the final output for instant playback.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect CodaDocs, packs, automations.
- 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.