SUMMARIZATION
Run a full audiobook production pass with a CEO agent overseeing QA
On manual kickoff, an agent reads a source manuscript, plans chapters, narrates them with ElevenLabs, runs a length-and-coverage QA check, retries weak chapters.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator manually kicks off production run
- ActionAgent reads manuscript and plans chaptersOpenAI
- ActionElevenLabs narrates each planned chapterElevenLabs
- LogicQA chapters for length and coverage; flag failures
- ActionAgent re-narrates flagged chapters until QA passesElevenLabs
- OutputPublish finished audiobook and manifest to DropboxDropbox
What it does
Orchestrates an end-to-end audiobook production run under agent supervision. The agent ingests a manuscript, plans the chapter structure, narrates every chapter with ElevenLabs, then QAs the output for coverage and length gaps, automatically re-narrating any chapter that fails, before publishing the finished set with a manifest.
When to use it
Use it for a one-shot, supervised production of a complete title where you want judgment in the loop — handling odd front matter, footnotes, or uneven chapters — rather than a rigid block pipeline. Best when you kick off a single book and want a vetted deliverable back.
How it works
- 1An operator manually starts the production run and points it at the manuscript.
- 2The agent reads the document, plans chapters, and resolves front matter and footnotes.
- 3ElevenLabs narrates each planned chapter.
- 4A QA logic step compares each chapter's audio against expected length and text coverage.
- 5The agent re-narrates any chapter flagged below threshold, looping until QA passes or a retry cap is hit.
- 6The finished chaptered audiobook and a production manifest are published to Dropbox.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect ElevenLabsText-to-speech, voice cloning.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.