DATA OPS

On-Demand Stale Dashboard Report by Team

Triggered by a Slack slash command with a team name, returns a ranked list of that team's dashboards unused in 90 days, with view counts and owners, posted as a threaded report.

CategoryData Ops
Enginesim
Difficultybeginner
Triggerchat
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack slash command with a team nameSlack
  • ActionRun team-scoped BigQuery staleness queryGoogle BigQueryBigQuery
  • LogicReturn a friendly note if no stale dashboards
  • LogicFormat results into a ranked owner/last-viewed table
  • OutputPost the report as a threaded Slack replySlack

What it does

Gives any manager a self-serve way to audit their team's dashboard footprint on demand. A Slack slash command carrying a team or folder name kicks off a BigQuery query scoped to that team, ranks their dashboards by staleness, and replies in-thread with a clean table of zero-view-in-90-days dashboards, their owners, and last-viewed dates — no waiting for the scheduled org-wide sweep.

When to use it

Use this when a team lead wants an immediate read on their own dashboard sprawl ahead of a planning cycle or reorg, without filing a ticket to the data team. It complements the scheduled sweeps with an interactive, scoped lookup.

How it works

  1. 1A Slack slash command with a team argument triggers the flow.
  2. 2BigQuery runs a usage query filtered to that team's dashboards, sorted by days since last view.
  3. 3A guard returns a friendly message if the team has no stale dashboards.
  4. 4The flow formats the results into a ranked table with owner and last-viewed columns.
  5. 5The report is posted back as a threaded reply to the invoking Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.