DATA OPS
Dashboard Decommission Sweep: Zero-View Keep/Archive Decision
Weekly scan of BigQuery dashboard view logs finds dashboards with zero views in 90 days and DMs each owner a Slack keep-or-archive decision with one-click buttons.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the sweep
- ActionQuery BigQuery for dashboards with 0 views in 90 days + ownerBigQuery
- LogicFilter out dashboards already decided in a prior sweep
- ActionDM each owner a Slack keep/archive prompt with buttonsSlack
- ActionWrite the owner's decision back to BigQueryBigQuery
What it does
Queries your BI tool's view/access logs warehoused in BigQuery, isolates every dashboard that has not been opened by any user in the last 90 days, and routes each stale dashboard to its owner as a private Slack message with Keep and Archive buttons. Owner responses are logged back to BigQuery so the sweep never re-pings a dashboard someone already decided on.
When to use it
Run this when your BI workspace has accumulated hundreds of dashboards and nobody knows which are still load-bearing. Ideal for data platform teams doing quarterly cleanup who want owners — not the data team — to make the keep/archive call.
How it works
- 1A weekly schedule fires the sweep.
- 2BigQuery runs a query joining the dashboard catalog against access logs, returning dashboards with 0 views in 90 days plus their owner email.
- 3A filter drops any dashboard already resolved in a prior sweep.
- 4For each remaining dashboard, Slack DMs the owner an interactive Keep/Archive prompt.
- 5The owner's choice is written back to a BigQuery decisions table for audit and dedupe.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.