DATA OPS
Owner-Resolution Agent for Orphaned Stale Dashboards
For zero-view dashboards whose owner is missing or has left the company, an agent infers the most likely current owner from query authorship and team membership.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers the orphan pass
- ActionQuery BigQuery for ownerless zero-view dashboards + authorsBigQuery
- LogicAgent infers likely owner with a confidence score
- LogicBranch: high-confidence to nominee, low to data team
- ActionSend the Slack keep/archive request to the recipientSlack
- OutputRecord inferred ownership in NotionNotion
What it does
Handles the hardest dashboards in any decommission sweep: the orphans whose listed owner is blank, a shared service account, or an employee who has left. An agent pulls each orphaned dashboard's underlying query history and recent collaborators from BigQuery, reasons about who most plausibly owns it now, and routes a keep/archive decision to that best-guess owner — escalating to the data team only when confidence is low.
When to use it
Use this alongside the standard sweep to clear the long tail of ownerless dashboards that a simple owner-lookup flow can't route. Best for organizations with churn where the original creator is often gone.
How it works
- 1A weekly schedule triggers the orphan pass.
- 2BigQuery returns zero-view dashboards with no valid current owner, plus their query authors and last editors.
- 3The agent weighs authorship recency and team signals to nominate a likely owner with a confidence score.
- 4A branch routes high-confidence cases to the nominee and low-confidence cases to the data team channel.
- 5The chosen recipient receives a Slack keep/archive request, and the inferred ownership is recorded in Notion.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect NotionPages, databases, comments.
- 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.