CONTENT CREATION
Weekly Loom walkthrough digest into a Notion KB with Slack rollup
On a weekly schedule, collects all new Loom recordings, drafts a help-doc for each with extracted screenshots, files them under the right Notion knowledge-base section.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionList new Loom recordings and fetch transcriptsLoom
- ActionDraft help-doc and propose KB section (OpenAI)OpenAI
- ActionCapture step screenshots from each recordingLoom
- ActionFile drafts into Notion knowledge baseNotion
- OutputPost weekly digest to SlackSlack
What it does
Runs once a week to sweep up every new Loom walkthrough, turn each into a screenshot-backed help-doc draft, and file them into the correct section of your Notion knowledge base. It finishes by posting one Slack digest summarizing all the docs created that week.
When to use it
Use it when recordings pile up faster than anyone documents them and you'd rather batch the work than handle each video individually. The weekly cadence and single digest keep noise low while ensuring nothing recorded goes undocumented.
How it works
- 1A weekly schedule triggers the workflow.
- 2All Loom recordings created since the last run are listed and their transcripts fetched.
- 3For each recording, an OpenAI model drafts a help-doc and proposes the matching knowledge-base category.
- 4A screenshot is captured at each step's timestamp and embedded in the draft.
- 5Each draft is filed under its proposed section in the Notion knowledge base.
- 6A single rollup of all docs created is posted to a Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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 Content Creation workflows
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.
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.
On-demand: turn a blog URL into narrated B-roll clips
Accepts a blog URL via webhook, scrapes the article, generates a B-roll clip per paragraph with Replicate and a voiceover with ElevenLabs.
On-Demand Screenshot Freshness Report from a Slack Command
A writer requests a freshness check in Slack for a specific docs page; the workflow inspects every screenshot on that page, scores each by age and version gap.
Sync a Figma master frame into localized hero renders
Pulls the current master hero frame and its text layers from Figma, generates a localized image variant for each locale defined in Airtable.
Research-driven localized hero banners tuned per market
An agent researches cultural and seasonal cues for each target market, adapts the master hero concept to fit local context, generates a tailored image per locale.
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.