DATA OPS
BigQuery Failure Webhook to Trello and PagerDuty Bridge
Receives a BigQuery failure alert via inbound webhook, severity-routes it, and either opens a low-priority Trello card or pages on-call through PagerDuty while still creating…
How it runs
The automated pipeline, trigger to output.
- TriggerInbound BigQuery failure webhookHTTP webhook
- LogicMap query to severity tier
- ActionPage on-call for critical tierPagerDuty
- ActionOpen priority-matched Trello cardTrello
- OutputConfirm routing in DiscordDiscord
What it does
Turns raw BigQuery log-based alert webhooks into the right response by severity. Failures on tier-3 internal queries become a quiet Trello card; failures on revenue- or SLA-critical queries page PagerDuty immediately and open a high-priority card so the incident is tracked from the first second.
When to use it
Use it when BigQuery alerts arrive from Cloud Monitoring or a log sink as webhooks and you need one place to decide what wakes someone up versus what waits for the next workday. It enforces a consistent severity policy across every query owner.
How it works
- 1An inbound HTTP webhook receives the BigQuery failure alert payload.
- 2A logic step parses the query name and maps it to a severity tier from a maintained criticality list.
- 3Critical-tier failures trigger a PagerDuty incident with the error summary and a deep link.
- 4Every failure, regardless of tier, opens a Trello card with priority matching its severity for durable tracking.
- 5A Discord message confirms the routing decision so the team can see what was paged versus queued.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect TrelloKanban boards for everything.
- 4Connect DiscordCommunity channels + voice + bots.
- 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.