SUMMARIZATION
Re-narrate chapters when a pronunciation lexicon changes
Triggers on edits to a pronunciation lexicon doc, finds chapters containing the changed terms, re-narrates only those chapters with ElevenLabs using the updated lexicon.
How it runs
The automated pipeline, trigger to output.
- TriggerPronunciation lexicon doc editedDropbox
- ActionScan chapter source files for changed termsDropbox
- LogicBuild impacted-chapter set; exit if none match
- ActionElevenLabs re-narrates impacted chapters with new lexiconElevenLabs
- ActionOverwrite affected audio and refresh index durationsDropbox
- OutputNotify Slack of re-rendered chapters and reasonSlack
What it does
Keeps an audiobook consistent when names and jargon get corrected. When the pronunciation lexicon changes, the workflow finds exactly which chapters contain the affected terms, re-narrates only those chapters with the updated lexicon applied, and swaps the new audio in place — no full-book re-render.
When to use it
Use it for technical or name-heavy books where pronunciations get refined over time. It avoids the cost and turnaround of re-narrating an entire title every time one term is fixed, while guaranteeing every occurrence is corrected.
How it works
- 1An edit to the pronunciation lexicon doc fires the trigger with the changed terms.
- 2The flow scans the chapter source files in Dropbox for those terms.
- 3A logic step builds the impacted-chapter set and exits early if nothing matches.
- 4ElevenLabs re-narrates each impacted chapter applying the updated lexicon.
- 5The new files overwrite the prior chapter audio in Dropbox, and the TTS index durations are refreshed.
- 6A notification posts to Slack listing which chapters were re-rendered and why.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect ElevenLabsText-to-speech, voice cloning.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.