DATA OPS
Snowflake Row-Volume Anomaly Watch
Compares each morning's load row count for key Snowflake tables against a trailing 14-day baseline and alerts Slack when volume spikes or collapses beyond a threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily after loads complete
- ActionCount last-24h rows per table in SnowflakeSnowflake
- ActionPull trailing 14-day baseline from SnowflakeSnowflake
- LogicFlag deviation beyond percent band
- OutputAlert Slack with count, baseline, and deltaSlack
What it does
Detects silent data-volume anomalies that freshness checks miss. For each watched Snowflake table it counts rows loaded in the last 24 hours, compares that to the median of the prior 14 daily loads, and flags any table that loaded far more or far fewer rows than usual, which usually signals a duplicated load, a partial extract, or a dropped source.
When to use it
When a table updates on time but with the wrong amount of data, like a partner feed that delivered half its rows or a job that double-inserted. Freshness looks green while the numbers are quietly broken. Use this to catch volume drift before it reaches reports.
How it works
- 1A daily schedule fires once loads complete.
- 2The flow queries Snowflake for last-24h row counts per watched table.
- 3It pulls the trailing 14-day daily counts and computes the median baseline.
- 4A logic step flags tables where today's count deviates beyond the configured percent band.
- 5Flagged tables post to Slack with today's count, the baseline, and the percentage delta so an analyst can confirm or dismiss.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.
