DATA OPS
Reverse-ETL Failure Webhook: Triage Severity and Page On-Call
Receives a sync-failure webhook from your reverse-ETL tool, classifies the failure by reject rate.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook fires on reverse-ETL run failureHTTP webhook
- LogicCompute reject rate and classify severity
- ActionRecord reject-rate metric to Datadog for trend trackingDatadog
- LogicBranch: route by severity threshold
- OutputOpen PagerDuty incident for high-severity failuresPagerDuty
What it does
This workflow listens for the failure callback your reverse-ETL platform fires when a sync run ends with rejected rows. It computes the reject rate against total rows, decides whether the failure is routine noise or a real incident, and routes accordingly so on-call only gets paged for genuine breakage.
When to use it
Use this when every minor sync hiccup currently pages someone at 3am. It adds a severity gate so a handful of bad emails stays quiet, but a connector outage or schema break escalates immediately.
How it works
- 1An incoming webhook fires when the reverse-ETL run completes with failures.
- 2The flow parses the payload for total rows, rejected rows, and the failure category.
- 3A logic step computes reject rate and compares it to your severity thresholds.
- 4Below threshold, it records the event to a Datadog metric for trend tracking and stops.
- 5At or above threshold, it opens a PagerDuty incident with the connector name, reject count, and a sample error.
- 6The incident links back to the failing run so the responder lands on the right place.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect DatadogMetrics, traces, log search.
- 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.