DATA OPS
Schema-Drift Gate Before Snowflake DDL Deploy
Triggered by a webhook from your CI pipeline, it checks whether the target Snowflake table already drifted from its BigQuery source before applying new DDL.
How it runs
The automated pipeline, trigger to output.
- TriggerCI pre-deploy webhook with table nameHTTP webhook
- ActionRead BigQuery source schemaBigQuery
- ActionRead Snowflake target schemaSnowflake
- LogicDecide pass or block on drift
- OutputReturn allow/block decision to CIHTTP webhook
What it does
This workflow acts as a pre-deploy guard. When CI is about to apply DDL to a Snowflake table, it first confirms the table still matches its authoritative BigQuery schema. If unexpected drift is present, it fails the gate and returns the conflicting columns so the pipeline stops before layering a new migration on top of an inconsistent base.
When to use it
Use it when manual hotfixes or out-of-band ALTERs sometimes hit Snowflake directly, and you want CI to refuse to deploy until the table is reconciled with BigQuery. It prevents migrations from silently compounding drift.
How it works
- 1An HTTP webhook from the CI pipeline triggers the check with the target table name.
- 2It reads the BigQuery schema for that table.
- 3It reads the current Snowflake schema for the same table.
- 4A logic step compares them and decides pass or fail.
- 5The webhook responds with an allow/block decision plus the offending columns, which CI uses to halt or proceed.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 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
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 orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
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.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
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.
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…
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.