ENGINEERING
Detect live API drift from the published OpenAPI contract on a schedule
On a daily schedule, fetch the running API's live OpenAPI document and compare it to the source-of-truth spec in your repo; if the deployed surface has drifted, open a GitHub…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionFetch live OpenAPI document from running serviceHTTP webhook
- ActionRead canonical spec from repositoryGitHub
- LogicDiff live vs canonical; stop if no drift
- ActionOpen GitHub issue describing the driftGitHub
- OutputPage API on-call via PagerDutyPagerDuty
What it does
Periodically pulls the OpenAPI document served by your live API and diffs it against the canonical spec committed in your repository. Any divergence (an endpoint live but undocumented, a field removed in production but still in the spec, a changed type) is flagged as drift.
When to use it
Use it when your published contract and your running service can fall out of sync because deploys outpace doc updates. It catches the dangerous gap where consumers trust a spec that no longer matches production behavior.
How it works
- 1A scheduled trigger runs the check on your chosen cadence (e.g. daily).
- 2An HTTP request fetches the live OpenAPI document from the running service.
- 3The flow reads the canonical spec from the GitHub repository.
- 4A diff step compares live versus canonical and isolates drift items.
- 5A logic branch exits quietly if there is no drift; otherwise it continues.
- 6It opens a GitHub issue detailing each drift and triggers a PagerDuty alert for the API on-call.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.