DATA OPS
Agent-Driven PII Drift Investigation with Confluence Dossier
An agent investigates newly detected sensitive columns across BigQuery, traces their likely source and downstream consumers, drafts a governance dossier in Confluence.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule launches the investigation
- ActionPull new columns and samples from BigQueryBigQuery
- LogicAgent classifies data and estimates blast radius
- ActionDraft governance dossier page in ConfluenceConfluence
- OutputOpen linked Linear review and assign ownerLinear
What it does
This is an agent-led workflow that goes beyond flagging a column. When new sensitive fields surface, the CEO agent investigates context — what the column likely contains, which jobs read it, and the regulatory category — then writes a structured governance dossier and opens a review linked to it.
When to use it
Use it for high-stakes governance programs where a bare ticket isn't enough and reviewers need an analyzed brief: provenance, blast radius, and a recommended classification ready before the meeting.
How it works
- 1A weekly schedule launches the investigation run.
- 2The agent pulls new columns and value samples from BigQuery against the prior baseline.
- 3For each candidate, it reasons over column names, sampled values, and table lineage to classify the data and estimate downstream exposure.
- 4It drafts a Confluence page per finding — evidence, likely source system, affected consumers, and a proposed sensitivity tier.
- 5It opens a Linear issue linking the dossier and assigns the governance owner for sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.