CONTENT CREATION
Agent-run docs pipeline: triage a Loom recording and route it to the right destination
On a new Loom recording, an agent reads the transcript, decides whether it is a public help article, an internal runbook, or a bug repro, and routes a drafted version to ReadMe.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom recording processedLoom
- ActionAgent fetches transcript and timestampsLoom
- LogicAgent classifies intent and chooses destination
- ActionDraft and route to ReadMe, Confluence, or LinearReadMe
- OutputPost routing summary to SlackSlack
What it does
Uses an agent to interpret each new Loom recording rather than forcing one fixed output. The agent reads the transcript, classifies the recording's intent, drafts the appropriate document, and sends it to the matching system: customer-facing how-tos go to ReadMe, internal procedures to Confluence, and anything describing a defect becomes a Linear issue with the repro steps and Loom link.
When to use it
For orgs where recordings serve mixed purposes and you don't want a separate workflow per outcome. Let the agent decide where each video belongs and produce the right artifact.
How it works
- 1A new Loom recording fires the trigger.
- 2The agent fetches the transcript and chapter timestamps from Loom.
- 3The agent classifies intent: public help article, internal runbook, or bug report.
- 4Based on the decision, it drafts the correctly formatted document for that destination.
- 5It routes the output, creating a ReadMe draft, a Confluence page, or a Linear issue.
- 6It posts a summary of what it created and why to Slack for oversight.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect ReadMeAPI docs, changelog, auth.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
Full multi-format snippet pack from one episode
An agent takes a published episode and produces a complete repurposing pack: quote cards, show notes, audiogram scripts, and a thread, organized into a Notion hub page.
Guest recap email draft after episode publish
When an episode publishes, transcribe it, draft a personalized thank-you email to the guest with their best quotes and shareable links, and queue it as a Gmail draft.
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Audiogram script and clip-timestamp builder
From a transcript dropped in Drive, pick three viral-worthy 30-to-60-second segments, write captions and hook text, and post the clip plan to Slack for editors.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
Podcast episode to branded quote cards
When a new episode audio file lands in Drive, transcribe it, pull the five most quotable lines, and generate branded quote-card images ready to post.
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.