CONTENT CREATION

Published RSS Episode to YouTube Chapters and Description

When a new episode publishes to your podcast RSS feed, transcribe its audio and generate a YouTube-ready description with timestamped chapter markers.

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerwebhook
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew episode published to RSS feedHTTP webhook
  • ActionFetch episode audio and transcribe with timestampsElevenLabsElevenLabs
  • ActionGenerate YouTube description and chapter markersOpenAI
  • OutputWrite YouTube-ready doc to Google DriveGoogle DriveGoogle Drive

What it does

Bridges your audio podcast and its YouTube counterpart. As soon as an episode goes live on the feed, it builds the exact description and chapter block YouTube needs, so whoever uploads the video version just copies it in instead of re-listening to mark chapters.

When to use it

Use it when you publish each episode to both a podcast host and YouTube and want the YouTube chapters to match the audio without manual timeline scrubbing. Triggering off the live RSS feed means it runs automatically right after release.

How it works

  1. 1A new item in the podcast RSS feed triggers the flow via webhook.
  2. 2The episode's audio URL is fetched and transcribed by ElevenLabs with timestamps.
  3. 3OpenAI writes a YouTube description and a chapter list formatted in YouTube's required 0:00 syntax, where the first chapter starts at zero.
  4. 4A Google Drive document is created with the description and chapter block ready to paste into the video upload.

Set it up

What you configure once, before turning it on.

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