DATA OPS
Reverse-ETL Schema-Change Impact Alert
Watches Snowflake for column renames, drops, or type changes in tables that feed reverse-ETL syncs and warns the data team in Microsoft Teams which downstream CRM fields will…
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule triggers the schema inspection
- ActionQuery current columns and types from Snowflake schemaSnowflake
- LogicDiff against snapshot for renamed, dropped, retyped columns
- LogicMap breaking changes to affected downstream CRM fields
- OutputWarn the data team in Microsoft Teams with impact listMicrosoft Teams
What it does
Most reverse-ETL breakages start upstream: someone renames or drops a Snowflake column that a sync mapping depends on, and the CRM field goes stale or null on the next run. This workflow gets ahead of that. On a schedule it inspects the schema of the warehouse tables that back your sync mappings, compares it to the last recorded snapshot, and detects any renamed, dropped, or retyped columns. It then resolves which downstream CRM fields each affected column maps to and warns the data team before the damage propagates.
When to use it
Use it when warehouse models change often and analysts editing dbt or tables can unknowingly break a CRM sync mapping. Run nightly or after each model deploy.
How it works
- 1A schedule triggers the schema inspection.
- 2Snowflake INFORMATION_SCHEMA query returns current columns and types for mapped tables.
- 3A logic step diffs against the stored snapshot to find renamed, dropped, or retyped columns.
- 4A second logic step maps each breaking change to the downstream CRM fields it feeds.
- 5If impact is found, a Microsoft Teams message names the column, the change, and the CRM fields at risk so the mapping is fixed before the next sync.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.