CONTENT CREATION

Narrate new Markdown blog drafts dropped into Dropbox

Watches a Dropbox folder for new Markdown blog files, narrates them with ElevenLabs using chapter markers from the headings.

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerevent
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew file added to watched Dropbox folderDropboxDropbox
  • LogicFilter to Markdown (.md) files only
  • ActionParse front matter and split body by heading
  • ActionNarrate each chapter with ElevenLabsElevenLabsElevenLabs
  • LogicMerge clips and embed chapter markers
  • OutputWrite MP3 + chapters.txt to Dropbox /audioDropboxDropbox

What it does

Monitors a Dropbox folder where writers save long-form Markdown posts. Each new file is narrated end to end with chapter markers derived from its headings, and the resulting MP3 lands in an /audio subfolder next to the source.

When to use it

Use it when your writing workflow is file-based (Markdown in Dropbox, Obsidian-synced, or exported drafts) and you want an audio version generated automatically without a CMS. Ideal for solo creators and small editorial teams.

How it works

  1. 1A Dropbox file-added event fires when a new .md file appears in the watched folder.
  2. 2The flow filters to Markdown files only, skipping images and other assets.
  3. 3It parses the Markdown, stripping front matter and splitting the body into chapters at each heading.
  4. 4Each chapter is narrated with ElevenLabs and the per-chapter durations are recorded.
  5. 5Clips are merged into one MP3 and an embedded chapter track is generated from the timestamps.
  6. 6The MP3 and a sidecar chapters.txt are written to the /audio folder in Dropbox.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect ElevenLabsText-to-speech, voice cloning.
  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.