DATA OPS
Route Schema-Change Webhooks to the Right dbt Owner by Severity
Receives a schema-change webhook from your ingestion tool, traces which dbt models depend on the changed table.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives schema-change eventHTTP webhook
- ActionMap changed table to dependent dbt models and owners
- LogicGrade severity: breaking vs additive
- OutputPage on-call via PagerDuty for breaking changesPagerDuty
- OutputPost low-key Slack note for additive changesSlack
What it does
Accepts a real-time webhook fired by your data-ingestion connector when it detects an upstream schema change. It maps the changed table to dependent dbt models, scores the change's severity, and routes the alert to the right place: an urgent page for breaking changes, a low-key Slack message for harmless additions.
When to use it
Use it when your loader (Fivetran, Airbyte, or similar) already emits schema-change events and you want push-based, severity-aware routing instead of polling. Ideal for teams that page on-call only for changes that can actually break a build.
How it works
- 1An HTTP webhook receives the schema-change event from the ingestion tool.
- 2The payload is normalized and the changed table is matched to its dependent dbt models and owners.
- 3A logic step grades severity: dropped or retyped columns are breaking, new nullable columns are additive.
- 4Breaking changes trigger a PagerDuty incident routed to the owning team's on-call.
- 5Additive changes post a non-urgent Slack note to the team channel for awareness only.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.