AI AGENTS
Weekly Loom backlog to Coda SOP index
On a weekly schedule, finds all new Loom recordings from the past week, drafts an SOP for each, and appends them as rows to a single Coda SOP index table for batch review.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionList new Loom recordings and fetch transcriptsLoom
- ActionDraft an SOP per recordingHugging Face
- ActionAppend SOP rows to Coda indexCoda
- OutputPost weekly digest summary to SlackSlack
What it does
Runs once a week, sweeps every Loom recording made in the last seven days, drafts a written SOP for each, and logs them all as rows in a Coda index table so a manager can review the week's knowledge in one place.
When to use it
Use it when recordings pile up faster than anyone documents them and you'd rather process the backlog in a weekly batch than react to each video. The Coda table becomes a living register of which procedures are captured, drafted, and still pending review.
How it works
- 1A weekly schedule trigger fires (e.g. Friday afternoon).
- 2The agent lists all Loom recordings created since the last run and fetches each transcript.
- 3For each recording a Hugging Face model drafts a concise SOP summary and step list.
- 4The agent appends one row per video to the Coda SOP index, with title, draft body, source link, and a 'needs review' status.
- 5A Slack summary message reports how many new SOP drafts landed in Coda and links the table.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect CodaDocs, packs, automations.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.