DATA OPS
ELT pipeline-finished webhook to Datadog event and Teams alert
When your orchestrator posts its nightly run-finished webhook, this records the outcome as a Datadog event for trend tracking and, on any failed or skipped model.
How it runs
The automated pipeline, trigger to output.
- TriggerOrchestrator run-finished webhookHTTP webhook
- LogicParse run summary and failed models
- ActionEmit Datadog event with status tagsDatadog
- LogicBranch on failed or skipped models
- OutputPost failure detail to TeamsMicrosoft Teams
What it does
Turns your ELT orchestrator's end-of-run webhook into observable signal. It parses the run summary (success/error/skip counts and per-model results), emits a structured Datadog event tagged by run status and environment so you can chart failure rates over time, and on failure pushes a Teams message naming the failed models and their first-line errors.
When to use it
Use it when your scheduler reports run results via webhook but nobody watches its UI. You want failures in the channel the team already lives in, plus a Datadog timeline to spot "this model fails twice a week" patterns.
How it works
- 1The orchestrator's run-finished webhook triggers the flow with the run payload.
- 2A logic step parses the summary into pass/fail/skip and a list of failed model names.
- 3A Datadog event is emitted with status tags and counts for dashboards and monitors.
- 4A branch checks whether any model failed or was skipped.
- 5On failure, a Teams alert is posted with the failed models and their error snippets.
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 Microsoft TeamsChannels, chats, files.
- 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.