DATA OPS
Daily BigQuery Scheduled-Query Health Digest
Runs every morning, scans the last 24 hours of BigQuery scheduled-query runs, and posts a Discord digest of failures, retries, and chronic flaky queries.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionPull 24h scheduled-query run historyBigQuery
- LogicAggregate counts, flag chronic offenders
- ActionOpen deduped Trello card per offenderTrello
- OutputPost health digest to DiscordDiscord
What it does
Gives data teams a once-a-day rollup of every scheduled query's health instead of a stream of individual alerts. It counts failures and successes over the trailing day, flags queries that failed more than once, and distinguishes one-off blips from chronically flaky configs that need real attention.
When to use it
Use it when you run dozens of scheduled queries and want trend visibility rather than per-event noise. It is the calm morning report that tells you what quietly broke overnight and which pipelines are degrading over time.
How it works
- 1A daily schedule trigger fires each morning before standup.
- 2An action pulls the run history for all scheduled queries in the project over the last 24 hours.
- 3A logic step aggregates per-query success and failure counts and marks any query with repeated failures as a chronic offender.
- 4For each chronic offender it opens a Trello card (deduplicated against existing open cards) so it does not get lost in the digest.
- 5It posts a formatted Discord digest summarizing total runs, failures, recoveries, and the offender list.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect DiscordCommunity channels + voice + bots.
- 3Connect TrelloKanban boards for everything.
- 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.
