AI AGENTS
Loom walkthrough to Confluence SOP draft
When a new Loom recording is published, transcribe it and draft a clean step-by-step SOP page in Confluence marked 'Draft - needs review', then ping the author in Slack to approve.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom video publishedLoom
- ActionFetch transcript and timestampsLoom
- ActionSummarize transcript into ordered SOP stepsHugging Face
- ActionCreate draft SOP page in ConfluenceConfluence
- OutputDM author in Slack to review and publishSlack
What it does
Turns a screen-recorded Loom walkthrough into a structured written SOP and parks it in Confluence as a draft awaiting human sign-off. No one has to re-watch the video and type out the steps.
When to use it
Use it when subject-matter experts explain processes by recording Loom videos but your team needs searchable written procedures. Ideal for support runbooks, onboarding guides, and tool walkthroughs where the knowledge currently lives only in someone's screen recording.
How it works
- 1A new Loom video published in the watched workspace fires the trigger and passes the share URL.
- 2The agent pulls the recording's transcript and timestamps from Loom.
- 3A Hugging Face summarization model converts the spoken transcript into ordered, imperative SOP steps with section headings.
- 4The agent creates a Confluence page in the SOP space titled with the video name, prefixed 'Draft - needs review', embedding the source Loom link.
- 5A Slack DM goes to the video author with the page link asking them to verify and publish.
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 ConfluenceSpaces, pages, blueprints.
- 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.