DATA OPS
App-DB migration drift watcher to Linear
Tracks the live column shape of your application's Postgres tables and, when it diverges from the schema your analytics ingestion expects, creates a Linear ticket assigned…
How it runs
The automated pipeline, trigger to output.
- TriggerPost-deploy schedule fires
- ActionRead current columns from app Postgres tablesPostgres
- LogicDiff against tracked shape, filter to pipeline-referenced columns
- OutputCreate Linear issue for the data teamLinear
- ActionUpdate tracking table with new shapePostgres
What it does
Monitors the boundary where product engineers ship Postgres migrations that the analytics ingestion layer hasn't accounted for. It compares the app database's current columns against the schema your pipeline reads from and files a Linear ticket when a migration introduces, removes, or renames a column the pipeline cares about.
When to use it
Product ships migrations weekly and your analytics sync breaks every time someone renames a column without telling data. You want those renames to land as tracked work in Linear, not as a surprise during the next sync.
How it works
- 1A scheduled trigger runs after the product team's typical deploy window.
- 2Read the current column list from the application Postgres tables your pipeline ingests.
- 3Compare against the last-recorded shape stored in a Postgres tracking table.
- 4A logic step isolates columns the ingestion pipeline actually references and flags drift on those.
- 5If a referenced column changed, create a Linear issue describing the migration impact and assign the data team.
- 6Update the tracking table with the new shape.
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.