ENGINEERING

Nightly audit of deployed API specs for undocumented breakage

Each night fetches the live OpenAPI spec served by each deployed environment, compares it to the last-known-good snapshot in Postgres.

CategoryEngineering
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires
  • ActionFetch live served spec per environmentHTTP webhook
  • ActionLoad approved baseline specPostgreSQLPostgres
  • LogicDiff each environment for breaking drift
  • OutputAlert Teams on drift or refresh baselineMicrosoft Teams

What it does

Catches breaking changes that slipped past code review by inspecting what is actually running. On a schedule it pulls the live spec from each environment's endpoint, diffs it against the approved baseline stored in Postgres, and reports any backward-incompatible drift, including changes from out-of-band hotfixes or config.

When to use it

Use it when specs can change at runtime or when you do not fully trust merge-time gates, and you want a safety net that verifies deployed reality against the contract every night.

How it works

  1. 1A nightly schedule starts the run.
  2. 2For each environment, the workflow fetches the served OpenAPI spec over HTTP.
  3. 3It loads the last-approved baseline spec for that environment from Postgres.
  4. 4A diff-and-classify step checks each environment for breaking drift.
  5. 5If any environment drifted incompatibly, it sends a Microsoft Teams alert naming the environment and changes; otherwise it updates the baseline snapshot.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.