DOCUMENT OPS
Stale SOP Refresh from Re-Recorded Loom
When a Loom video tagged to an existing SOP is re-recorded, this diffs the new walkthrough against the current doc and updates only the steps that changed.
How it runs
The automated pipeline, trigger to output.
- TriggerRe-recorded Loom tagged to a docLoom
- ActionFetch new transcript and live doc contentConfluence
- LogicDiff walkthrough vs doc, gate on material change
- ActionRewrite changed steps and regenerate screenshotsImage generation
- OutputPatch Confluence page with revision noteConfluence
- OutputNotify owner of what changedSlack
What it does
Keeps existing SOPs in sync with reality. When someone re-records the Loom for a process that already has a documented runbook, this compares the new transcript against the live doc, identifies which steps changed, and patches just those sections — updating screenshots and bumping the doc's version note rather than rewriting the whole page.
When to use it
Use it when processes drift and SOPs silently rot. Instead of full rewrites, you get targeted, auditable updates whenever a refreshed Loom lands. Ideal for compliance-sensitive ops where you need to know exactly what changed and when.
How it works
- 1A re-recorded Loom carrying an existing-doc tag triggers the run.
- 2The flow fetches the new transcript and the current Confluence page content.
- 3A logic step diffs the two and decides whether changes are material enough to update.
- 4If material, an agent rewrites only the affected steps and regenerates their screenshots.
- 5It updates the Confluence page in place, appends a dated revision note, and preserves unchanged sections.
- 6A summary of what changed is posted to the doc owner.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect Image generationManaged Nano Banana image renders, metered per image.
- 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 Document Ops workflows
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
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.