DATA OPS
Nightly staging-vs-prod schema drift to Linear migration ticket
Compares the column and index definitions between your staging and production Postgres databases every night and, when they diverge, opens a Linear migration-review ticket…
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionRead staging schema catalogPostgres
- ActionRead production schema catalogPostgres
- LogicDiff schemas; exit if identical
- ActionFormat the DDL diff into a migration brief
- OutputOpen Linear migration-review issueLinear
What it does
Every night this workflow snapshots the `information_schema` of both your staging and production Postgres instances, diffs them table-by-table, and files a Linear ticket whenever staging has drifted ahead of (or behind) production. The ticket body contains the precise DDL difference so a reviewer can approve the migration without hunting it down.
When to use it
Use it when staging is your migration proving ground and you want a paper trail before anything reaches prod. It catches the classic failure mode where a developer altered staging directly and forgot to write the production migration.
How it works
- 1A nightly schedule fires the run.
- 2Query `information_schema.columns` and `pg_indexes` from staging.
- 3Query the same catalogs from production.
- 4Diff the two snapshots; if they are identical, the run exits quietly.
- 5When drift exists, format the added/dropped/altered objects into a readable migration brief.
- 6Open a Linear issue in the migration-review project with the diff attached and label `schema-drift`.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
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.