CONTENT CREATION

Render multi-voice podcast audio from a Dropbox script file

Watches a Dropbox folder for new dialogue scripts, generates a distinct ElevenLabs voice for each speaker, stitches the lines into one episode file.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew script file in Dropbox folderDropboxDropbox
  • LogicParse script into speaker-tagged lines
  • LogicMap each speaker to an ElevenLabs voice
  • ActionSynthesize each line in its assigned voiceElevenLabsElevenLabs
  • ActionConcatenate clips into one episode track
  • OutputUpload finished MP3 to Dropbox episodes folderDropboxDropbox

What it does

Monitors a Dropbox "scripts" folder for new conversational scripts written as speaker-tagged lines, then produces a fully voiced episode — each character rendered in its own ElevenLabs voice — and writes the assembled MP3 back to a Dropbox "episodes" folder.

When to use it

Use this for narrative blog content, dialogue explainers, or two-host show notes where a single flat voice won't do. Drop a script in, get a multi-voice render out, with no audio editor in the loop.

How it works

  1. 1A new file landing in the Dropbox scripts folder triggers the flow.
  2. 2The script is parsed into ordered lines, each tagged with a speaker name.
  3. 3A branch maps every speaker to its assigned ElevenLabs voice id.
  4. 4ElevenLabs synthesizes each line in the correct voice, preserving order.
  5. 5The clips are concatenated into a single episode track with short gaps between turns.
  6. 6The finished MP3 is uploaded to the Dropbox episodes folder, named to match the source script.

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.