DATA OPS
Partner CSV to Snowflake with Threshold-Based PagerDuty Alert
Validates a scheduled partner CSV against a schema, loads clean rows into Snowflake, quarantines rejects to S3.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled partner CSV pull
- LogicValidate rows against contract schema
- ActionLoad clean rows into SnowflakeSnowflake
- ActionWrite rejected rows + defect report to S3AWS S3
- LogicCompute reject rate vs threshold
- OutputOpen PagerDuty incident if threshold breachedPagerDuty
What it does
This workflow validates a partner CSV against your contract schema, loads the clean rows into Snowflake, and writes rejected rows to an S3 quarantine prefix. Unlike a fire-on-every-defect setup, it only escalates when the reject rate exceeds a threshold you define (for example, more than 5 percent of rows bad) — so routine noise stays quiet and real feed breakage pages someone.
When to use it
Use it when partner feeds always have a little dirt but a sudden spike in rejects signals an upstream schema change or a broken export. The threshold gate turns the workflow into an early-warning system for feed integrity.
How it works
- 1A scheduled trigger pulls the partner CSV.
- 2Each row is validated against the schema contract.
- 3Clean rows are loaded into the Snowflake target table.
- 4Rejected rows and a defect report are written to S3 quarantine.
- 5A logic step computes the reject rate and compares it to the threshold.
- 6If the threshold is breached, a PagerDuty incident is opened with the run stats and top failure reasons.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.