CONTENT CREATION

Weekly agent that repurposes recent episodes into a kit

On a weekly schedule, an agent reviews episodes published that week, drafts a newsletter blurb, blog outline, and discussion thread for each.

CategoryContent Creation
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionQuery Notion for episodes published this weekNotionNotion
  • LogicExit if no new episodes found
  • ActionDraft newsletter, blog, and thread per episode
  • ActionAssemble repurpose kit in ConfluenceConfluenceConfluence
  • OutputEmail host for sign-offGmailGmail

What it does

A weekly content agent that looks back at the episodes you shipped, then builds a repurposing kit per episode: a newsletter blurb, a blog post outline, and a community discussion thread. It organizes everything in Confluence and emails the host to approve.

When to use it

Run it every Friday to keep a steady drip of derivative content from your back catalog without a weekly planning meeting. Best for shows that struggle to repurpose episodes beyond the initial launch push.

How it works

  1. 1A weekly schedule starts the agent.
  2. 2The agent queries Notion for episodes published in the last seven days.
  3. 3If no new episodes exist, it exits quietly; otherwise it proceeds per episode.
  4. 4For each episode the agent drafts a newsletter blurb, a blog outline, and a discussion-thread prompt from the show notes.
  5. 5It assembles the drafts into a structured Confluence page per episode.
  6. 6It emails the host a summary with links for sign-off.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect GmailRead, draft, send, label.
  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.