DATA OPS
Nudge an author in Slack the moment a single BigQuery query crosses a slot-cost ceiling
Watches finished BigQuery jobs in near-real-time and, when any single query exceeds the slot-cost ceiling, immediately DMs its author a Slack message with the query, its cost…
How it runs
The automated pipeline, trigger to output.
- TriggerShort-interval schedule for new jobs
- ActionQuery JOBS finished since last run by slot_msBigQuery
- LogicFilter to over-ceiling, not-yet-nudged queries
- OutputDM author the query, cost, and cheaper tipSlack
- ActionRecord nudged job IDs to dedupePostgres
What it does
It catches expensive queries while they're still fresh in the author's mind. The workflow polls recently completed BigQuery jobs on a short interval, and the instant one query blows past your slot-cost ceiling, it DMs the author a focused nudge — the exact SQL, what it cost, and a concrete suggestion — so feedback lands within minutes instead of the next morning.
When to use it
Use it when daily summaries arrive too late to change behavior and you want immediate, low-friction coaching on outlier queries. Best for high-volume analytics teams where one runaway scan can starve everyone else's queries.
How it works
- 1A short-interval schedule checks for newly finished jobs.
- 2Query `INFORMATION_SCHEMA.JOBS` for jobs completed since the last run, sorted by slot_ms.
- 3Filter to queries whose individual slot cost exceeds the ceiling and that haven't been nudged yet.
- 4For each, derive a cheaper-pattern tip from the query shape.
- 5DM the author in Slack with the query, cost, and tip.
- 6Record the nudged job IDs to avoid duplicate alerts.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.