DOCUMENT OPS

Batch-narrate a Google Drive PDF folder in multiple languages

On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled nightly run
  • ActionList PDFs in the Drive folderGoogle DriveGoogle Drive
  • LogicKeep only PDFs missing an audio version
  • ActionTranslate text per configured languageOpenAI
  • ActionGenerate per-language narration with ElevenLabsElevenLabsElevenLabs
  • OutputSave MP3s into per-language Drive subfoldersGoogle DriveGoogle Drive

What it does

Runs on a schedule across a Google Drive folder of published PDFs. For any document missing an audio version, it extracts the text and produces ElevenLabs narrations in every language you configure, saving each into its own language subfolder. One run keeps an entire library audio-ready and localized.

When to use it

Use it when you publish PDFs for a multilingual audience and need spoken versions in several languages. The scheduled batch model suits libraries that grow in bursts rather than a steady trickle, and it backfills anything added since the last run.

How it works

  1. 1A scheduled trigger kicks off the run (for example, nightly).
  2. 2The Drive folder is listed and each PDF is checked against existing audio outputs.
  3. 3A loop processes only PDFs with no narration yet.
  4. 4For each configured language, the text is translated and sent to ElevenLabs with the matching voice.
  5. 5Each MP3 is written to a per-language subfolder in Google Drive, mirroring the source filename.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect ElevenLabsText-to-speech, voice cloning.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.