ENGINEERING
Alert dependent service owners when an API breaks
When a breaking OpenAPI change merges, looks up which downstream services consume the affected endpoints and DMs each service owner in Microsoft Teams with the exact fields…
How it runs
The automated pipeline, trigger to output.
- TriggerPush to main changes the API specGitHub
- ActionDiff spec and extract broken endpoint pathsGitHub
- ActionQuery dependency registry for consuming servicesPostgres
- LogicGroup breaks by owning team
- OutputDM each affected owner in Microsoft TeamsMicrosoft Teams
What it does
Turns a merged breaking change into targeted, actionable warnings. After an API spec change lands on the main branch, it identifies the endpoints that broke, queries a dependency registry for the services that call those endpoints, and notifies each owning team in Microsoft Teams individually rather than spamming one shared channel.
When to use it
Use it in a multi-team org where several services depend on a shared API and you need owners to find out the moment a contract changes, not when their integration starts failing in production.
How it works
- 1A push to the default branch with a changed spec triggers the run.
- 2The workflow diffs the spec and extracts the list of broken or removed endpoint paths.
- 3It queries a Postgres dependency registry mapping endpoints to consuming services and their owners.
- 4For each affected service it composes a per-owner message with the changed fields and a migration deadline.
- 5It sends a direct Microsoft Teams message to each owner.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect Microsoft TeamsChannels, chats, 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 Engineering workflows
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.
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.
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.
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.
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…
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.