ENGINEERING
Alert downstream teams when a new API spec is published
When a new version of the OpenAPI spec is released, diff it against the previously published version and notify each consuming team in Slack with only the changes that touch…
How it runs
The automated pipeline, trigger to output.
- TriggerNew spec version publishedHTTP webhook
- ActionLoad new and prior published specsShell
- ActionDiff specs into per-path change listShell
- LogicFilter to teams with relevant changes
- OutputPost scoped change notice per teamSlack
What it does
Turns a spec release into targeted change notices. Instead of broadcasting a full changelog to everyone, it diffs the newly published spec against the last one and routes a per-team Slack message containing only the changed paths each team consumes.
When to use it
Use this when many internal services depend on one shared API and a generic "new version is out" announcement gets ignored. Scoping the message to a team's own dependencies makes the alert actionable and raises the odds they update before the next breaking release.
How it works
- 1A spec-published webhook fires (from your release pipeline or registry).
- 2The flow loads the new spec and the previously published version.
- 3A shell step diffs the two and produces a per-path change list.
- 4It joins changed paths against a consumer registry mapping paths to owning teams and Slack channels.
- 5A logic branch drops teams with no relevant changes.
- 6For each remaining team, it posts a scoped Slack message naming the changed endpoints and whether each change is breaking.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 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 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.
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…
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.
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.