CONTENT CREATION

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.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew draft file added to Dropbox folderDropboxDropbox
  • ActionRead file and split into paragraphsDropboxDropbox
  • ActionRender a B-roll clip per paragraph with ReplicateReplicateReplicate
  • ActionUpload clips to a per-post Dropbox subfolderDropboxDropbox
  • OutputWrite a paragraph-to-clip manifest fileDropboxDropbox

What it does

Converts blog drafts dropped into a watched Dropbox folder into a tidy, downloadable B-roll library. Each paragraph becomes a short generated clip, and the workflow files all clips for a post into their own Dropbox subfolder so editors can scrub a finished library instead of chasing links.

When to use it

Use it when writers export posts as Markdown or text into a shared Dropbox and your video editors work from local files in Premiere or CapCut rather than from a CMS. Ideal for agencies that hand off raw assets to clients.

How it works

  1. 1A Dropbox file-added trigger fires when a new draft appears in the watched 'blog-drafts' folder.
  2. 2The file contents are read and split into paragraphs.
  3. 3Replicate generates a short B-roll clip for each paragraph from its summary.
  4. 4Each rendered MP4 is uploaded into a Dropbox subfolder named after the source post.
  5. 5A manifest text file listing paragraph-to-clip mappings is written alongside the clips for the editor.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect ReplicateImage, video, and model inference.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.