MARKETING

Auto-Voice New Ad Scripts Dropped Into a Dropbox Folder

Watches a Dropbox intake folder for new script files, generates the configured set of regional ElevenLabs voiceovers for each, and saves the rendered audio alongside the source.

CategoryMarketing
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew script file added to Dropbox intake folderDropboxDropbox
  • ActionRead the script's text content from DropboxDropboxDropbox
  • LogicParse campaign tag, skip empty or already-processed scripts
  • ActionRender a regional voiceover variant per config region in ElevenLabsElevenLabsElevenLabs
  • OutputWrite MP3s to audio/ and move source to processed/ in DropboxDropboxDropbox

What it does

Makes a Dropbox folder a drop zone for scripts. The moment a copywriter saves a new `.txt` or `.docx` script into the watched folder, the workflow reads it, generates the full set of regional voiceover variants, and writes the audio back into a sibling `audio/` folder next to the script.

When to use it

Use it when your team already lives in Dropbox and you want zero new tools in the loop — no forms, no tickets. Save a script, come back to finished voiceovers. Great for fast-moving creative shops producing many short scripts.

How it works

1. A Dropbox file-added trigger fires when a new script lands in `/Scripts/intake/`. 2. The workflow reads the file's text content. 3. A logic step parses the filename for a campaign tag and validates the script isn't empty or already processed. 4. For each region in your standing config, ElevenLabs renders a voiceover variant. 5. Every MP3 is written to `/Scripts/intake/audio/{campaign}-{region}.mp3`. 6. The source script is moved to a `processed/` subfolder so it isn't voiced twice.

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.