DATA OPS
Post-ingestion freshness verification on pipeline webhook
On a pipeline-completion webhook, verifies the expected Snowflake tables actually advanced their load timestamps and row counts; if any did not move, it flags a silent-failure…
How it runs
The automated pipeline, trigger to output.
- TriggerPipeline-completion webhookHTTP webhook
- ActionRead loaded_at + row_count for expected tablesSnowflake
- LogicDetect tables that did not advance (silent failure)
- OutputAlert owning team on silent failuresSlack
What it does
A pipeline can report success while silently writing zero rows or skipping a table. This workflow catches that: when your orchestrator fires its done webhook, it immediately checks that each expected table's load timestamp and row count actually advanced since the previous run, and raises a silent-failure alert when they didn't.
When to use it
Use it right after batch loads where green pipeline status is not enough proof, especially when downstream SLAs depend on the load truly landing data this cycle.
How it works
- 1An HTTP webhook from your orchestrator triggers the run with the batch's table list and prior watermark.
- 2A Snowflake query reads current `loaded_at` and `row_count` for each expected table.
- 3A logic step compares against the supplied watermark to detect tables that did not advance or whose row delta is zero.
- 4If everything advanced, the run records success and exits quietly.
- 5For any silent failures, a Slack alert tags the owning team with the offending tables and deltas.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 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.