DATA OPS
On-Demand Schema Drift and Freshness Pre-Flight Check
A webhook-triggered check that a dbt or pipeline job calls before publishing, verifying source BigQuery tables are both fresh and structurally unchanged.
How it runs
The automated pipeline, trigger to output.
- TriggerPre-flight webhook from upstream jobHTTP webhook
- ActionFetch load times + column schemasBigQuery
- LogicCheck freshness + schema fingerprint
- LogicSet pass/fail status for caller
- OutputAlert Teams on failure with reasonMicrosoft Teams
What it does
Acts as a pre-flight gate for downstream jobs. When a pipeline or dbt run calls the webhook before it starts, this workflow verifies two things about each source BigQuery table: that it loaded within its freshness window and that its column schema matches the recorded expected fingerprint. If a table is stale or its schema drifted, the check returns a fail status and posts the reason to Microsoft Teams, letting the caller abort before propagating bad or incompatible data.
When to use it
Use this when a transformation job must never run on stale or structurally changed inputs, for example a nightly model build feeding executive reporting where a silent schema change would corrupt output.
How it works
- 1A webhook from the upstream job triggers the run with the target table list.
- 2A BigQuery action fetches last-load times and current column schemas.
- 3A logic step compares freshness against SLA and schema against the stored fingerprint.
- 4A branch sets a pass or fail status the caller reads from the response.
- 5On failure, a Microsoft Teams message names the offending table and the specific reason.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect Microsoft TeamsChannels, chats, files.
- 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.