CONTENT CREATION

Article to two-host conversational podcast episode

Manually run on a chosen article, this rewrites it as a two-host dialogue, voices each speaker with a distinct ElevenLabs voice, merges the tracks, and saves the episode to S3.

CategoryContent Creation
Enginesim
Difficultyadvanced
Triggermanual
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator runs on a selected article
  • ActionRewrite article into two-host dialogue with OpenAIOpenAI
  • ActionRender each speaker with its own ElevenLabs voiceElevenLabsElevenLabs
  • LogicStitch speaker turns into one ordered track
  • OutputSave merged MP3 and transcript to S3AWS S3

What it does

Converts a single article into a conversational, two-host podcast episode. It rewrites the source into a natural back-and-forth script, assigns each speaker a separate ElevenLabs voice, renders both turns, and merges them into one continuous MP3 ready for your feed.

When to use it

Use it when a flat single-narrator read feels dry and you want the engaging interview style of popular AI-generated shows. Best for explainer and deep-dive posts that benefit from a host asking the questions a listener would.

How it works

  1. 1An operator manually starts the run and selects the source article.
  2. 2OpenAI rewrites the article into an alternating two-speaker dialogue script with speaker tags.
  3. 3Each speaker's lines are sent to ElevenLabs using that speaker's assigned voice.
  4. 4The rendered turns are stitched in order into a single MP3.
  5. 5The finished episode and its transcript are saved to S3 for publishing.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OpenAIModels, embeddings, files.
  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.