DEVOPS
Flag merged BigQuery queries over budget and open a Linear tuning task
When a PR merges, scans changed SQL for BigQuery queries whose dry-run cost exceeds your byte budget and opens a Linear task with the offending diff and a dry-run estimate.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request mergedGitHub
- ActionFetch diff and filter changed .sql filesGitHub
- ActionDry-run each query to estimate bytes scannedBigQuery
- LogicKeep only queries over the byte budget
- OutputOpen Linear tuning task with diff and estimateLinear
What it does
Every merged pull request becomes a cost gate. The flow pulls the SQL files changed in the merge, runs each query as a BigQuery dry run to estimate bytes scanned, and compares that against a configured budget. Any query over budget gets a Linear task containing the exact diff, the estimated cost, and the PR link so an engineer can tune it before it runs at scale.
When to use it
Use it when analytics or pipeline SQL ships through GitHub and you keep getting surprised by expensive on-demand queries after merge. It catches regressions at the moment they land, not weeks later on the bill.
How it works
- 1A GitHub pull request merged event fires the flow.
- 2The flow fetches the diff and filters to changed .sql files.
- 3Each query runs as a BigQuery dry run to read estimated bytes processed.
- 4A logic step keeps only queries above the byte budget.
- 5For each offender, a Linear issue is created with the diff snippet, the dry-run estimate, and the PR URL, labeled for the data platform team.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect LinearIssues, projects, cycles, triage.
- 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 DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.