DATA OPS
Alert On-Call When a Tagged PII Column Disappears
Detects when a previously classified PII column is dropped or renamed in Snowflake and pages the on-call data engineer via PagerDuty.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled scan interval
- ActionQuery current Snowflake column inventorySnowflake
- LogicFind known PII columns now missing
- LogicBranch only if columns disappeared
- ActionOpen PagerDuty incidentPagerDuty
- OutputPost heads-up to SlackSlack
What it does
This workflow watches for the disappearance of columns that were previously confirmed as PII. When a tagged sensitive column is dropped or renamed between scans, it raises a PagerDuty incident so the on-call engineer can confirm the change was intentional and verify that retention, deletion, and consumer obligations are still met.
When to use it
Use it when removing a PII column has real consequences — broken right-to-be-forgotten pipelines, orphaned downstream joins, or audit-trail gaps. Additions get reviewed; deletions often go unnoticed until something downstream breaks. This closes that blind spot.
How it works
- 1A scheduled trigger starts the scan.
- 2Query the current Snowflake column inventory and compare it to the prior snapshot's set of known PII columns.
- 3A logic step isolates PII columns present before but missing now (dropped or renamed).
- 4If any disappeared, branch into alerting; otherwise exit quietly.
- 5Open a PagerDuty incident naming each removed PII column, its former table, and last-seen timestamp.
- 6Post a parallel heads-up to the data-governance Slack channel for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.