DATA OPS
Approved Dashboard Retirement with Snapshot Archive to S3
Triggered when a reviewer approves a retirement in Coda, it snapshots the dashboard definition to S3 cold storage, archives it in Snowflake metadata, and confirms back in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerCoda webhook fires on retirement approvalCoda
- LogicVerify status is Approved and not already archived
- ActionWrite dashboard snapshot to S3 cold storageAWS S3
- ActionMark asset Archived in Snowflake with restore pathSnowflake
- OutputPost retirement confirmation to SlackSlack
What it does
When a reviewer flips a dashboard to Approved-for-Retirement in Coda, this workflow safely decommissions it: it preserves a snapshot of the dashboard definition in S3, marks the asset archived in Snowflake, and posts a confirmation to the team channel.
When to use it
Run this as the action half of a decay program. The sweep finds candidates; this executes the retirement only after a human approves, with a recoverable archive so nothing is lost permanently.
How it works
- 1A Coda automation webhook fires when a row's status becomes Approved.
- 2A guard confirms the row is genuinely Approved and not already archived.
- 3The dashboard's definition and last-known metadata are written as a timestamped object to an S3 archive bucket.
- 4Snowflake's dashboard registry row is updated to status Archived with the S3 location and retirement date.
- 5Slack posts a confirmation to the data-ops channel naming the dashboard, who approved it, and the restore path.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect SnowflakeWarehouses, queries, shares.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
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 orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
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.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
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.
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…
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.