DATA OPS
BigQuery DDL Webhook Drift Triage with Agent Severity Call
Receives BigQuery audit-log DDL events via webhook in near real time, has an agent assess the change against the table's documented contract and downstream consumers.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives BigQuery DDL audit eventHTTP webhook
- ActionFetch affected table schema and metadataBigQuery
- ActionAgent reads documented contract from NotionNotion
- LogicBranch on agent severity rating
- ActionPage on-call for high-severity driftPagerDuty
- OutputOpen ClickUp review task for lower-severity driftClickUp
What it does
It reacts to schema changes the moment they land instead of waiting for a nightly scan. A Cloud Logging sink posts BigQuery DDL audit events to a webhook. An agent reads the changed table's documented contract and its known downstream consumers, then judges severity: does this drop or retype a column something depends on? High-severity drift pages on-call; lower-severity drift opens a review task for the contract owner to confirm during business hours.
When to use it
Use it for high-traffic warehouse environments where waiting until the nightly run to learn about a breaking `ALTER TABLE` is too slow, and where a human judgment call on blast radius beats a rigid rule. Good for teams that already export BigQuery audit logs to a sink.
How it works
- 1A webhook receives a BigQuery DDL audit-log event.
- 2Fetch the affected table's current schema and metadata from BigQuery.
- 3The agent reads the documented contract from Notion and weighs downstream impact.
- 4Branch on the agent's severity rating.
- 5High severity pages on-call via PagerDuty.
- 6Lower severity opens a ClickUp review task with the agent's assessment.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect NotionPages, databases, comments.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Connect ClickUpDocs + tasks + chats in one workspace.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Snowflake column type-drift sentinel with Linear fix ticket
Snapshots the data types of every column in your tracked Snowflake schemas on a schedule, diffs against the last snapshot.
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 dropped/renamed column sentinel with PagerDuty incident
Detects when a column is dropped or renamed in your governed BigQuery datasets and, because that breaks downstream queries hard, pages the on-call via PagerDuty and posts…
PR-time Snowflake schema contract check on dbt model changes
When a pull request changes a dbt model, it compares the model's declared output columns against the live Snowflake table it will replace and blocks the merge with a GitHub check…
Agent-triaged warehouse drift with impact analysis and runbook update
On a webhook from your warehouse audit log, an agent investigates the changed column, traces which downstream models and dashboards depend on it.
Cross-warehouse replication schema mismatch reconciler
Compares the column shape of mirrored tables between BigQuery and Snowflake and, when a replicated table has drifted out of sync between the two, opens an Asana task for the data…
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.