DATA OPS
Breaking Snowflake Column Changes to ClickUp Review Tasks
Detects only breaking schema changes on Snowflake tables (dropped or retyped columns) and opens a triaged ClickUp migration-review task assigned to the table owner.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule triggers warehouse scan
- ActionRead Snowflake schema and compare to baselineSnowflake
- LogicClassify changes; pass only breaking ones
- LogicResolve table owner from contract metadata
- OutputCreate assigned ClickUp migration-review taskClickUp
What it does
Watches your warehouse for the schema changes that actually break downstream queries — columns that disappear or change type — and turns each one into a ClickUp task in your migration-review list. Purely additive changes (new nullable columns) are classified as safe and skipped, so the queue stays meaningful.
When to use it
Reach for this when your data team already lives in ClickUp and you want a low-noise review queue that only fills up when something will genuinely break a dashboard, model, or reverse-ETL sync.
How it works
- 1A schedule triggers a warehouse scan.
- 2Snowflake `INFORMATION_SCHEMA` is read for the tracked table set and compared to the stored baseline.
- 3A logic step classifies each change as additive (safe) or breaking (dropped/retyped/narrowed); only breaking changes pass.
- 4For each breaking change it looks up the table owner from the contract metadata.
- 5It creates a ClickUp task with the before/after column shape, severity, and owner as assignee, then updates the stored baseline.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 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
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.