SUMMARIZATION
Backfill an entire Loom demo archive into the Coda transcript index
Run once to walk every existing video in a Loom folder, chapter and summarize each transcript with OpenAI.
How it runs
The automated pipeline, trigger to output.
- TriggerManual run with target Loom folder ID
- ActionList and page through all videos in the folderLoom
- LogicSkip videos already present in Coda index
- ActionFetch transcript and chapter+summarize with OpenAIOpenAI
- ActionInsert row into Coda transcript indexCoda
- OutputReport count of demos indexed
What it does
This is the one-time backfill that seeds your searchable library. It pages through every video already sitting in a Loom folder, fetches each transcript, generates chapters and a summary with OpenAI, and writes one Coda row per video so your full historical demo archive becomes searchable in a single run.
When to use it
Run this once when you first adopt the auto-chaptering setup and have hundreds of old demos that predate the live webhook. After the backfill completes, the per-video webhook flow keeps the index current going forward.
How it works
- 1A manual trigger starts the backfill with the target Loom folder ID.
- 2The flow lists all videos in the folder, paging until the archive is exhausted.
- 3A logic step skips any video whose Loom ID already exists as a Coda row, making the run safely re-runnable.
- 4For each remaining video it fetches the transcript and has OpenAI produce chapters and a summary.
- 5A Coda action inserts the row with transcript, chapters, and deep links; the final output reports how many demos were indexed.
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.