DATA OPS
dbt Run Failure Triage to Linear with Compiled SQL
Catches failed dbt model builds from a webhook, extracts the failing node and its compiled SQL plus BigQuery error.
How it runs
The automated pipeline, trigger to output.
- Triggerdbt run-results webhookHTTP webhook
- LogicKeep error + fail nodes only
- ActionRead compiled SQL artifactShell
- ActionFetch BigQuery job error detailBigQuery
- ActionOpen Linear bug to model ownerLinear
- OutputReturn issue URL to CI callerHTTP webhook
What it does
Listens for dbt run-result webhooks from your scheduler (dbt Cloud, Airflow, or a CI runner). When a model fails to build, it pulls the failing node's compiled SQL and the raw BigQuery error message, then opens a Linear bug assigned to the model's owner with a reproducible snippet attached.
When to use it
Use it when dbt build failures get lost in CI logs and the owning engineer finds out hours later. Ideal for teams running scheduled dbt jobs who want every red model to become an actionable, owned ticket automatically.
How it works
- 1A webhook receives the dbt run-results payload after each job.
- 2A filter keeps only nodes whose status is `error` or `fail`.
- 3For each failed node, a shell step reads the compiled SQL from the `target/compiled` artifact path.
- 4It queries BigQuery's job history to fetch the exact error and bytes-scanned at failure.
- 5It opens a Linear bug to the dbt `meta.owner`, embedding the compiled SQL and BigQuery error.
- 6It returns the created issue URL to the webhook caller for CI annotation.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect BigQueryDatasets, queries, schemas.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.