CONTENT CREATION

Weekly batch: process the episode backlog into kits and archive to Dropbox

On a weekly schedule, find unprocessed recordings in Dropbox, transcribe and generate chapters plus show notes for each, then write a Markdown kit back beside the original file.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionList recordings in Dropbox folderDropboxDropbox
  • LogicFilter to files with no kit yet
  • ActionTranscribe each pending recordingElevenLabsElevenLabs
  • ActionGenerate chapters + show notesOpenAI
  • OutputWrite Markdown kit back to DropboxDropboxDropbox

What it does

Sweeps your recording folder once a week and clears the backlog. For every recording that doesn't yet have a kit, it transcribes the audio, builds chapters and show notes, and writes a Markdown kit file right next to the original in Dropbox — so catching up is hands-off and self-contained.

When to use it

Use it when episodes pile up faster than you process them and you'd rather batch the work on a schedule than handle each file as it lands. Good for solo creators and small teams without a real-time pipeline.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2A Dropbox step lists recordings in the folder and a logic step filters to files that have no matching kit yet.
  3. 3For each remaining file, ElevenLabs transcribes the audio.
  4. 4An LLM step generates chapters and show notes from each transcript.
  5. 5The output step writes a Markdown kit file alongside the original recording in Dropbox.

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
    Connect NotionPages, databases, comments.
  4. 4
    Connect OpenAIModels, embeddings, 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.