DATA OPS
Audit dashboard queries against a changed BigQuery column
When a specific BigQuery column is dropped or retyped, scan logged dashboard and BI query history to list every query that still uses it.
How it runs
The automated pipeline, trigger to output.
- TriggerColumn-change webhookHTTP webhook
- ActionConfirm change via BigQuery INFORMATION_SCHEMABigQuery
- ActionSearch query history in Axiom for column referencesAxiom
- LogicGroup affected queries by dashboard and resolve owners
- OutputNotify dashboard owners in Microsoft TeamsMicrosoft Teams
What it does
Focuses the blast radius on the BI layer rather than dbt. When a tracked column changes, it searches your queried-from logs in Axiom (where you ship BigQuery job and dashboard query metadata) to find every saved query, scheduled report, or dashboard tile that referenced the column, and warns the people who own those dashboards.
When to use it
Use it when schema changes don't break pipelines but silently break charts — a renamed column makes a tile go blank or a filter stop working, and nobody notices until an exec asks why a number is gone. This catches the BI fallout that dbt-only checks miss.
How it works
- 1A webhook fires from your schema-tracking step when a column is dropped or retyped in BigQuery.
- 2The workflow confirms the change against BigQuery `INFORMATION_SCHEMA`.
- 3It queries Axiom for recent query logs that referenced the table and column.
- 4A logic step groups matching queries by dashboard and resolves each dashboard's owner.
- 5It sends each owner a Microsoft Teams message listing their affected dashboards and the column that moved.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect AxiomLog streams, queries, dashboards.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.