DATA OPS
Drift detected, Slack approval, then auto-file the migration ticket
Detects staging-vs-prod schema drift on demand, posts the diff to a Slack channel with Approve/Ignore buttons, and only opens a Linear migration ticket once a human approves.
How it runs
The automated pipeline, trigger to output.
- TriggerManual run
- ActionRead staging and prod schemasPostgres
- LogicDiff schemas; stop if no drift
- ActionPost diff to Slack with Approve/IgnoreSlack
- LogicBranch on reviewer decision
- OutputFile Linear migration ticket on approvalLinear
What it does
This workflow runs a staging-vs-production schema comparison, then routes the result through a human gate in Slack before anything lands in your tracker. The engineer on rotation sees the diff inline and clicks Approve to file a ticket or Ignore to dismiss expected drift (like a feature-flagged table that exists only in staging).
When to use it
Use it when fully automatic ticketing would bury your team in false positives. The Slack gate lets a human distinguish real migration debt from intentional, temporary divergence before it becomes backlog clutter.
How it works
- 1A manual or button-triggered run starts the comparison.
- 2Pull both staging and production schema catalogs from Postgres.
- 3Compute the diff; if empty, post a brief all-clear and stop.
- 4Post the rendered diff to Slack with Approve and Ignore actions.
- 5Branch on the reviewer's choice.
- 6On Approve, open a Linear migration-review ticket containing the diff.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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 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.