DATA OPS
dbt Run Webhook: Triage Failed Models and File Linear Tickets
Receives the dbt run-results webhook after each job, and for every failed or errored model it opens a deduplicated Linear issue pre-filled with the model, error, and downstream…
How it runs
The automated pipeline, trigger to output.
- Triggerdbt run-results posted to webhookHTTP webhook
- LogicFilter to models with error or fail status
- ActionResolve downstream dependents in SnowflakeSnowflake
- LogicSkip failures with an open ticket already
- OutputCreate a Linear issue per unique failureLinear
What it does
Listens for the webhook your orchestrator fires when a dbt run finishes. It parses the run results, isolates models with `error` or `fail` status, and for each one creates a Linear ticket scoped to the data team. The ticket includes the model name, the compiled error, and the list of downstream models that are now stale because of it, so the on-call engineer knows the blast radius immediately.
When to use it
Use when dbt failures currently get lost in CI logs and nobody owns the fix. This converts every failed model into a tracked, assignable unit of work with enough context to start debugging.
How it works
- 1The dbt orchestrator posts run-results to an HTTP webhook trigger.
- 2A logic step filters the results down to models whose status is error or fail.
- 3For each failure, a Snowflake lookup resolves the downstream dependents that the failure blocks.
- 4A dedupe check skips models that already have an open ticket this run cycle.
- 5A Linear issue is created per unique failure with error text, owner, and blast radius.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.