DATA OPS
Weekly Dashboard Decay Digest for Data Leadership in Teams
Aggregates the week's decay sweep results from BigQuery into a ranked leadership digest and posts a single summary card to a Microsoft Teams channel with totals and top offenders.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers the leadership digest
- ActionAggregate decayed dashboards and wasted compute in BigQueryBigQuery
- LogicRank teams by stale count and wasted spend
- LogicFormat headline totals and top offenders
- OutputPost the digest adaptive card to Microsoft TeamsMicrosoft Teams
- ActionAppend totals to a BigQuery trend tableBigQuery
What it does
Instead of pinging individual owners, this workflow rolls up the entire decay picture into one weekly executive digest — total stale assets, storage and compute they consume, and the worst offenders — and delivers it to data leadership in Microsoft Teams.
When to use it
Use this for the manager view: when leaders want a recurring pulse on BI hygiene and ROI rather than per-dashboard noise. It pairs well with the owner-nudge workflows that handle individual follow-up.
How it works
- 1A weekly schedule triggers the digest.
- 2BigQuery is queried to aggregate decayed dashboards by team, plus the compute cost of refreshing assets nobody views.
- 3A ranking step orders teams by stale-asset count and wasted spend.
- 4A formatting step builds a concise digest: headline totals, week-over-week change, and the top five offending teams.
- 5Microsoft Teams receives a single adaptive card posted to the leadership channel.
- 6The same totals are appended to a BigQuery trend table so the digest can show direction over time.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect Microsoft TeamsChannels, chats, files.
- 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.