CONTENT CREATION

Generate narration on CMS publish via webhook and call back the queue

Receives a publish webhook from your CMS, narrates the post body with ElevenLabs, stores the audio in Dropbox, and posts the public audio URL back to the publishing queue endpoint.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCMS publish webhook receivedHTTP webhook
  • LogicValidate payload has id, title, body
  • ActionSynthesize body text with ElevenLabsElevenLabsElevenLabs
  • ActionUpload MP3 to Dropbox and get linkDropboxDropbox
  • OutputPOST audio URL back to publishing queueHTTP webhook

What it does

Exposes a webhook your headless CMS calls whenever a post is published. It narrates the supplied body text with ElevenLabs, stores the resulting MP3 in Dropbox, and calls your publishing queue back with the audio URL so the live post can embed its voiceover automatically.

When to use it

Use this when your blog runs on a custom or headless CMS rather than Notion, and you want narration generated as part of the publish event itself — fully event-driven, with the audio link returned to whatever system tracks the queue.

How it works

  1. 1The CMS sends a publish webhook containing the post id, title, and body text.
  2. 2The flow validates the payload and rejects requests missing required fields.
  3. 3ElevenLabs synthesizes the body text into an MP3.
  4. 4The audio is uploaded to a Dropbox folder and a shareable link is generated.
  5. 5The flow calls back the publishing queue endpoint with the post id and audio URL, completing the loop.

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 DropboxFiles and folders.
  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.