DATA OPS
Auto-Archive Stale Dashboards After Owner Silence
When a dashboard's keep/archive decision deadline passes in Notion with no owner response, this flow auto-archives the dashboard via API, logs the action.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule checks for overdue decisions
- ActionQuery Notion for Pending rows past the archive-by dateNotion
- LogicSkip any row flipped to Keep since the deadline
- ActionCall the BI admin API to archive each dashboardHTTP webhook
- ActionSet the Notion row to ArchivedNotion
- OutputDM the owner on Slack with restore instructionsSlack
What it does
Closes the loop on the decommission process. It watches the Notion decommission register for rows whose archive-by deadline has passed while still marked Pending, then calls the BI platform's admin API to actually archive (not delete) those dashboards. The dashboard's metadata is preserved so it can be restored, the Notion row is moved to Archived, and the owner gets a courtesy heads-up.
When to use it
Use this as the enforcement stage after a register-building sweep. It prevents the common failure mode where owners ignore the decision request and stale dashboards linger forever — silence becomes a safe, reversible archive rather than indefinite limbo.
How it works
- 1A daily schedule checks for overdue decisions.
- 2Notion returns register rows that are Pending and past their archive-by date.
- 3A guard skips any row whose status changed to Keep in the meantime.
- 4The BI admin endpoint is called over an HTTP webhook to archive each dashboard.
- 5The Notion row is set to Archived and the owner is DMed on Slack with the restore instructions.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.