DATA OPS
Block warehouse exports sourced from stale BigQuery tables
Before a scheduled export copies BigQuery data into a downstream Postgres warehouse, it verifies every source table meets its freshness SLA and, if any is stale, aborts…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled export window
- ActionRead latest partition for every export sourceBigQuery
- LogicVerify all sources meet SLA; run-or-abort
- ActionRun export load into downstream warehousePostgres
- OutputAlert teams if export was skipped for stalenessSlack
What it does
It guards the boundary where data leaves BigQuery. Ahead of each scheduled export job, it checks the freshness of every source table the export depends on. If all are within SLA it runs the export into the downstream Postgres warehouse; if any source is stale it aborts, records the skip, and notifies the teams that would have consumed the data so no one builds on a partial copy.
When to use it
Use it when stale BigQuery data shouldn't be copied into a reverse-ETL target, reporting replica, or activation warehouse. Prevents bad data from spreading past the lakehouse.
How it works
- 1A schedule fires at each export window.
- 2A BigQuery action reads the latest partition timestamp for every source table in the export.
- 3A logic step verifies all sources meet SLA and decides run-or-abort.
- 4On pass, a Postgres action runs the export load into the downstream warehouse.
- 5On fail, a Slack message alerts data and consuming teams that the export was skipped and why.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.