DATA OPS
dbt Test-Failure Triage Agent from CI Webhook
Receives a dbt test-failure webhook from CI, has the CEO agent inspect the failing test, model lineage, and recent commits.
How it runs
The automated pipeline, trigger to output.
- TriggerReceive dbt CI test-failure webhookHTTP webhook
- ActionRead failing test SQL and model definitionGitHub
- ActionPull recent commits on model and parentsGitHub
- LogicMatch against existing open issues
- OutputCreate or comment Linear issue with hypothesisLinear
What it does
When a dbt build fails a test in CI, this workflow catches the webhook and lets the agent do the first pass of triage a human would: read the failed test name and SQL, trace the model's upstream lineage, scan the recent commits that touched it, and write a short hypothesis for why it broke. It then opens or comments on a Linear issue assigned to the likely owner.
When to use it
Use it when test failures pile up faster than your team can read them and most of the work is figuring out who broke what. The agent turns a red CI badge into a routed, explained ticket.
How it works
- 1A webhook trigger receives the dbt CI test-failure payload.
- 2The agent reads the failing test, its compiled SQL, and the model definition.
- 3It pulls recent commits touching the model and its parents from GitHub.
- 4A logic step decides whether this matches an existing open issue.
- 5The agent drafts a root-cause hypothesis and suggested owner.
- 6The result is written to Linear as a new issue or a comment on the existing one.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.