SUMMARIZATION
Quality-gate Loom demos and route weak transcripts for re-recording
When a Loom demo is chaptered into Coda, this scores the transcript for clarity and coverage with OpenAI.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom demo processedLoom
- ActionFetch transcript + chapters from Coda indexCoda
- ActionScore clarity and feature coverage with OpenAIOpenAI
- LogicBranch on pass/fail score threshold
- ActionFlag passing demo as published in CodaCoda
- OutputCreate Notion review card for failing demoNotion
What it does
After a Loom demo is transcribed and chaptered, OpenAI scores it on clarity, audio coverage, and whether it actually demonstrates the stated feature. High-scoring demos get marked published in Coda; weak ones are routed to a Notion review queue with the specific reasons they failed.
When to use it
Use this when demo quality is uneven and bad recordings keep leaking into your searchable library. It keeps the index trustworthy by catching mumbled, incomplete, or off-topic demos before they get surfaced in search.
How it works
- 1A Loom webhook fires on a newly processed demo video.
- 2The flow fetches the transcript and existing chapter data already written to the Coda index.
- 3OpenAI scores the transcript 0-100 on clarity and feature coverage and returns a pass/fail with reasons.
- 4A logic branch splits on the score threshold.
- 5Passing demos are flagged published in the Coda row; failing demos create a Notion review-queue card listing the gaps for the recorder to fix.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect CodaDocs, packs, automations.
- 4Connect NotionPages, databases, comments.
- 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.