ENGINEERING
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
How it runs
The automated pipeline, trigger to output.
- TriggerPhone-tree config PR merged in GitHubGitHub
- ActionFetch diff and extract changed prompt scriptsGitHub
- LogicDrop no-op edits; keep altered spoken lines
- ActionSynthesize changed lines with ElevenLabsElevenLabs
- ActionUpload new audio files to DropboxDropbox
- OutputOpen follow-up PR wiring in new audio pathsGitHub
What it does
Treats the IVR phone tree as code. When a pull request that edits the phone-tree config (script strings and node names) merges to the main branch, the workflow reads the diff, synthesizes audio for each changed prompt, uploads the clips, and opens a follow-up pull request that wires the new audio paths into the config.
When to use it
Use this when your IVR definition lives in a Git repo and product renames arrive as config edits. It guarantees the spoken audio is regenerated and version-tracked alongside the text it came from.
How it works
- 1A merged pull request touching the phone-tree config file triggers the run.
- 2A GitHub action fetches the diff and extracts prompts whose script text changed.
- 3A logic step skips no-op edits like reordering and keeps only altered spoken lines.
- 4ElevenLabs synthesizes the changed lines to audio files.
- 5An action uploads the audio to Dropbox and records the resulting paths.
- 6The output step opens a follow-up pull request updating the config to point at the new audio files.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ElevenLabsText-to-speech, voice cloning.
- 3Connect DropboxFiles and folders.
- 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 Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.