DATA OPS
Circuit Breaker for Snowflake-to-Attio Sync
Watches a Snowflake-to-Attio reverse-ETL run for a failure-rate spike, halts the sync when too many rows fail at once.
How it runs
The automated pipeline, trigger to output.
- TriggerSync batch result posted via webhookHTTP webhook
- LogicCompute failure ratio vs threshold
- ActionBelow threshold: retry failed rows into AttioAttio
- ActionAbove threshold: write pause flag to SnowflakeSnowflake
- OutputAlert on-call Teams channel that breaker trippedMicrosoft Teams
What it does
Not every failure should trigger a retry — sometimes a high failure rate means the upstream model is broken and you should stop pushing immediately. This workflow evaluates the failure ratio of a Snowflake-to-Attio sync batch. If the share of failing rows crosses a threshold, it trips a circuit breaker: it pauses further syncing, records the trip, and alerts on-call instead of mindlessly retrying garbage into your CRM.
When to use it
Use it as a safety wrapper around any high-volume reverse-ETL pipeline where a malformed warehouse model could otherwise overwrite thousands of good Attio records before anyone notices.
How it works
A webhook delivers the batch result with total and failed row counts. A logic step computes the failure ratio and compares it against your threshold. Below the threshold, individual failures are retried into Attio normally. Above it, the breaker trips: a flag row is written to Snowflake to pause downstream runs, and an urgent message goes to the on-call Microsoft Teams channel with the failure rate and a sample of errors so someone can investigate before resuming.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AttioReal-time CRM with structured data + powerful views.
- 3Connect SnowflakeWarehouses, queries, shares.
- 4Connect Microsoft TeamsChannels, chats, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.