DATA OPS
Reverse-ETL Freshness Triage Agent: Diagnose Stale Sync and File Linear Ticket
When a sync goes stale, an agent investigates the likely cause across warehouse query logs and ETL metadata, then files a Linear ticket with its diagnosis and pings Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerFreshness-breach webhook receivedHTTP webhook
- ActionPull BigQuery job history + ETL error metadataBigQuery
- LogicAgent weighs evidence and infers root cause
- ActionFile Linear ticket with diagnosis and fix suggestionLinear
- OutputNotify Slack with ticket link and cause summarySlack
What it does
This is an agent-driven triage workflow. When a reverse-ETL sync breaches its freshness budget, the agent gathers evidence — recent BigQuery job history, the model's last successful load, and error metadata — reasons about the most likely root cause, and opens a Linear ticket with its findings instead of just firing a raw alert.
When to use it
Use it when stale syncs need investigation, not just notification. The agent saves the first hour of debugging by assembling context and proposing a cause (upstream model failure, credential expiry, warehouse query error) before a human picks it up.
How it works
- 1A freshness-breach webhook fires with the stale model name and lag.
- 2The agent queries BigQuery job history and ETL metadata for that model's recent runs and errors.
- 3A logic step lets the agent weigh the evidence and pick the most probable root cause.
- 4The agent files a Linear ticket with the diagnosis, evidence links, and a suggested fix.
- 5A Slack message notifies the channel with the ticket link and one-line cause summary.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
Snowflake column type-drift sentinel with Linear fix ticket
Snapshots the data types of every column in your tracked Snowflake schemas on a schedule, diffs against the last snapshot.
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 dropped/renamed column sentinel with PagerDuty incident
Detects when a column is dropped or renamed in your governed BigQuery datasets and, because that breaks downstream queries hard, pages the on-call via PagerDuty and posts…
PR-time Snowflake schema contract check on dbt model changes
When a pull request changes a dbt model, it compares the model's declared output columns against the live Snowflake table it will replace and blocks the merge with a GitHub check…
Agent-triaged warehouse drift with impact analysis and runbook update
On a webhook from your warehouse audit log, an agent investigates the changed column, traces which downstream models and dashboards depend on it.
Cross-warehouse replication schema mismatch reconciler
Compares the column shape of mirrored tables between BigQuery and Snowflake and, when a replicated table has drifted out of sync between the two, opens an Asana task for the data…
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.