ENGINEERING
Nightly drift check: published spec vs live API responses
Each night, probe a sample of live API endpoints, compare the actual responses against the committed OpenAPI schema.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionFetch committed OpenAPI spec from GitLabGitLab
- ActionCall live endpoints and capture responsesHTTP webhook
- ActionValidate responses against schemaShell
- LogicDrift detected?
- OutputOpen GitLab issue for drifted endpointsGitLab
What it does
Validates that your deployed API still matches the OpenAPI spec checked into source control. It calls real endpoints, validates each response body and status against the schema, and reports fields the spec promises but the service no longer returns (or returns with a changed type).
When to use it
Use this when your spec is hand-maintained or generated separately from the implementation, so docs and reality silently diverge. A nightly run catches drift the day it ships instead of when an integrator files a support ticket.
How it works
- 1A nightly schedule triggers the run.
- 2The flow pulls the current OpenAPI spec from the GitLab repository.
- 3A shell step calls each sampled endpoint against the live base URL and captures responses.
- 4Each response is validated against its schema; mismatches are collected.
- 5A logic branch checks whether any drift was detected.
- 6If drift exists, the flow opens a GitLab issue with the offending paths, expected vs actual shapes, and assigns the owning team label.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 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.