DATA OPS
On-Demand Pre-Migration Schema Contract Check
Lets an engineer manually run a one-off comparison of a proposed Snowflake schema against the live table before a migration, returning a go/no-go contract verdict and, on conflict.
How it runs
The automated pipeline, trigger to output.
- TriggerEngineer manually triggers with proposed schema
- ActionFetch live table schema from SnowflakeSnowflake
- LogicDiff and evaluate against data contract for verdict
- OutputOpen Linear issue with blocking columns on no-goLinear
What it does
It gives engineers a self-serve safety check before they run a risky migration. The operator supplies the proposed DDL or target schema; the workflow fetches the current live schema from Snowflake, diffs the two, and evaluates whether the change would break the table's published data contract. It returns a clear go/no-go verdict inline and, when the verdict is no-go, files a Linear issue enumerating exactly which columns block the migration and why.
When to use it
Use it right before executing a manual schema migration or backfill, when you want a deterministic contract check on demand rather than waiting for the scheduled sentinel. It's the dry-run an engineer triggers themselves to avoid shipping a breaking `ALTER`.
How it works
- 1An engineer triggers the run manually with the proposed schema as input.
- 2Fetch the live table schema from Snowflake.
- 3Diff proposed against live and evaluate against the data contract.
- 4Branch on the verdict.
- 5On a clean verdict, return go inline; on conflict, open a Linear issue listing the blocking columns.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 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.