DATA OPS
Route dbt Run Failures to Downstream Dashboard Owners
When a dbt model fails, it traces every dashboard and table that depends on that model and pings each owner in Slack so the right people hear about broken data before…
How it runs
The automated pipeline, trigger to output.
- Triggerdbt run posts failure to webhookHTTP webhook
- ActionQuery Snowflake lineage for downstream dashboards + ownersSnowflake
- LogicBranch: owner-tagged vs fall back to on-call
- ActionDM each dashboard owner the impact in SlackSlack
- OutputPost team-channel summary of affected assetsSlack
What it does
Turns a raw dbt run failure into targeted, ownership-aware alerts. Instead of dumping a stack trace into one channel, it walks the lineage downstream of the failed model, finds which dashboards and marts are affected, and notifies the specific owner of each one.
When to use it
Use it when your dbt project feeds many BI dashboards and a single failing model silently breaks several of them. Ideal for analytics teams where dashboard ownership is distributed and a generic #data-alerts blast gets ignored.
How it works
- 1A dbt run posts its results to a webhook on failure.
- 2The flow reads the failed model's `unique_id` and queries Snowflake's information schema plus a lineage/exposures table to list every downstream dashboard and its owner.
- 3A branch checks whether any downstream exposure is owner-tagged; untagged ones fall back to the data on-call.
- 4For each affected dashboard, a Slack DM goes to its owner with the model name, error, and which of their dashboards is now stale.
- 5A summary message lands in the team channel for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 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.