OTHER
Incident-Resolved Voice Alert Routed by Affected Region
When an incident is marked resolved, generates a short reassurance voiceover in the affected regions' languages with ElevenLabs and posts it only to those regions' Slack channels.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook fires on incident-resolved with region listHTTP webhook
- LogicFilter to impacted regions; map language + channel
- ActionDraft all-clear script per affected languageOpenAI
- ActionGenerate voice alert MP3 per languageElevenLabs
- OutputPost voice alert to impacted regions' Slack channelsSlack
What it does
The moment an incident is flagged resolved, the workflow reads which regions were affected, drafts a brief customer-facing reassurance message, and generates an ElevenLabs voice alert in each of those regions' languages. The audio is posted only to the Slack channels for the impacted markets, so unaffected teams aren't pinged.
When to use it
Use this when a multi-region service has incidents that hit different markets and you want fast, spoken all-clear messaging tailored to who was actually down. It keeps comms targeted instead of blasting every region on every incident.
How it works
- 1A webhook fires when an incident is marked resolved, carrying the affected-region list and a summary.
- 2A logic step filters to only the regions that were actually impacted and maps each to its language and Slack channel.
- 3An OpenAI step drafts a short, calm all-clear script for each affected language.
- 4ElevenLabs renders each script into a voice alert MP3.
- 5The audio is posted to each impacted region's Slack channel as the resolution notice.
- 6A summary line confirms which regions received the alert for the on-call record.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ElevenLabsText-to-speech, voice cloning.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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 Other workflows
Sync IVR Prompt Registry in Airtable to Fresh ElevenLabs Audio
Runs nightly against an Airtable IVR prompt registry, finds rows whose script text changed since last synthesis, regenerates only those ElevenLabs clips.
Agent-Driven Full IVR Re-Voicing for a Rebrand
An agent takes a rebrand brief from Notion, audits every IVR prompt for old naming, rewrites and re-synthesizes the affected ones with ElevenLabs, archives them to Dropbox.
Regenerate IVR Voice Prompts When Notion Naming Doc Changes
Watches a Notion product-naming page and, whenever a product or feature name changes, regenerates the affected ElevenLabs IVR audio prompts and saves the new MP3s to Dropbox.
Pre-register a visitor, email a QR badge, and alert the host on arrival
When a host submits a visitor pre-registration form, this creates a visitor record, emails the guest a scannable QR badge with arrival instructions.
Sweep stale visitor check-ins, auto-checkout, and flag overdue guests
On a recurring schedule this finds visitors still marked on-site past their expected departure, auto-checks-out anyone past end-of-day.
Slack-Approved IVR Re-Voicing After a Product Rename
On demand from Slack, drafts updated IVR prompt scripts for a renamed product, posts them for human approval.
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.