DATA OPS
Real-Time Drift Alert from Warehouse DDL Webhook
Receives a DDL-change webhook from your warehouse event stream, instantly checks the altered table against the dbt contract.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives warehouse DDL-change eventHTTP webhook
- ActionQuery Snowflake for altered table's current shapeSnowflake
- LogicDiff current shape vs. dbt contract; check for conflict
- OutputPost Microsoft Teams alert with column-level diffMicrosoft Teams
What it does
Instead of waiting for a nightly sweep, this workflow reacts the instant a table changes. A webhook fires from your warehouse's DDL event stream carrying the altered table name. The workflow pulls that table's current shape, diffs it against the dbt contract, and if the change conflicts with the contract it posts a Microsoft Teams alert naming the column and the nature of the break within seconds of the ALTER.
When to use it
Use it when minutes matter and your warehouse can emit DDL events to a webhook. It is ideal for high-velocity environments where a mid-day schema change must reach the data team immediately rather than at the next scheduled scan, so they can intervene before downstream consumers read bad data.
How it works
- 1An HTTP webhook receives a DDL-change event with the affected table.
- 2Query Snowflake for the altered table's current column shape.
- 3Load the dbt contract for that specific model.
- 4Diff current shape vs. contract and decide if the change conflicts.
- 5If it conflicts, post a Microsoft Teams alert with the column-level diff and the originating change event.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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
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.