CONTENT CREATION

Back-catalog batch narration with Airtable progress tracker

Manually kicked off, this walks a backlog of published posts, narrates each that has no audio yet, uploads MP3s to S3, and logs status per episode in Airtable.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggermanual
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator starts batch run
  • ActionLoad candidate articles from AirtableAirtableAirtable
  • LogicSkip rows that already have audio
  • ActionNarrate remaining articles and upload MP3s to S3ElevenLabsElevenLabs
  • OutputWrite S3 URL and status back to AirtableAirtableAirtable

What it does

Narrates an entire back catalog of existing blog posts in one batch run. It reads a list of articles from Airtable, skips any that already have audio, narrates the rest with ElevenLabs, uploads each MP3 to S3, and writes the resulting URL and status back to the Airtable row so you always know what is done.

When to use it

Use it as a one-time or occasional catch-up job to give your archive a full audio version, or to backfill audio after launching a podcast feed. The Airtable tracker makes the long-running batch safe to resume.

How it works

  1. 1An operator manually starts the batch run.
  2. 2The flow loads candidate articles from the Airtable content table.
  3. 3For each row, it checks the audio field and skips ones already narrated.
  4. 4ElevenLabs narrates each remaining article and the MP3 is uploaded to S3.
  5. 5The S3 URL, duration, and Done status are written back to that Airtable row.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect ElevenLabsText-to-speech, voice cloning.
  3. 3
    Connect AWS S3Buckets, objects, signed URLs.
  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.