DATA OPS

Sync Dashboard Usage Decay into a Notion Lifecycle Registry

Pulls dashboard usage stats from BigQuery and upserts each dashboard's status (Active, Declining.

CategoryData Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule starts sync
  • ActionQuery 30/90-day usage from BigQueryGoogle BigQueryBigQuery
  • LogicClassify into Active / Declining / Abandoned
  • ActionLook up dashboard row in Notion registryNotionNotion
  • OutputUpsert status and metrics into NotionNotionNotion

What it does

Maintains a Notion database as the source of truth for dashboard lifecycle. On each run it pulls usage metrics from BigQuery, classifies every dashboard into a health tier, and upserts the row in Notion with last-viewed date, viewer count, and a Decay status property.

When to use it

Use this when leadership wants an always-current, browsable registry of every dashboard and its health, not just a one-off Slack ping. Good for orgs that already run governance docs in Notion and want decay tracked as a property rather than a report.

How it works

  1. 1A nightly schedule starts the sync.
  2. 2BigQuery returns per-dashboard usage over the trailing 30 and 90 days.
  3. 3A classification step maps metrics to a tier: Active, Declining, or Abandoned.
  4. 4The flow looks up each dashboard in the Notion registry by ID and upserts metrics plus the new status, preserving any manual owner notes.
  5. 5Output is the updated Notion database, ready for the team to filter on Abandoned and plan removals.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect NotionPages, databases, comments.
  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.