AI AGENTS
Length-Gated Narration Router for New Posts
Deterministically narrates only posts that exceed a reading-time threshold, posts a final-checks card to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: any post publishedHTTP webhook
- LogicCompute reading time and gate on length threshold
- ActionRender narration for long-form postsElevenLabs
- ActionSend Slack approval card with runtimeSlack
- OutputDeliver approved MP3 to DropboxDropbox
What it does
Applies a strict length gate before spending any audio credits: short posts are skipped and logged, long-form posts are narrated and sent for a final approval card before delivery.
When to use it
Use it when you only want narrations for genuinely long reads and need a clear, auditable rule for what got narrated and what was passed over.
How it works
- 1A webhook fires whenever any post is published.
- 2A logic step computes estimated reading time and branches: below threshold, log the skip reason and exit; at or above, continue.
- 3The cleaned article text is sent to ElevenLabs to produce the narration MP3.
- 4A Slack card shows the title, computed runtime, and an approve button for a quick final listen.
- 5On approval the MP3 is uploaded to Dropbox and the link is returned as the run output.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ElevenLabsText-to-speech, voice cloning.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect DropboxFiles and folders.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.