DATA OPS
Axiom Budget Alert Webhook to Realtime Throttle Ticket
Receives an Axiom monitor or budget webhook the moment ingestion crosses a spend guardrail, immediately attributes the burst to the loudest dataset and service.
How it runs
The automated pipeline, trigger to output.
- TriggerAxiom budget webhook receivedHTTP webhook
- ActionQuery Axiom burst window by serviceAxiom
- LogicBurst still active, not a settled blip?
- ActionOpen urgent Linear ticket with burn rateLinear
- OutputPage on-call in Slack with throttle tipSlack
What it does
Instead of waiting for a nightly batch, this workflow reacts the instant Axiom's own monitor fires a budget-threshold webhook. It queries Axiom for the live burst window, ranks the datasets and services driving it, and turns the alert into an actionable, attributed ticket within seconds.
When to use it
Use it when ingestion can spike fast enough to matter intraday, such as a retry storm or a debug-logging deploy, and you want the offender named before the burst runs for hours.
How it works
- 1An Axiom monitor posts to an inbound webhook when ingestion crosses the configured budget guardrail.
- 2The workflow parses the alert payload to extract the dataset and trigger time.
- 3Query Axiom for the burst window, grouped by service, to rank live contributors.
- 4A logic gate confirms the burst is still active rather than a settled blip.
- 5Open an urgent Linear ticket naming the dataset, top service, and current burn rate.
- 6Send a Slack page to on-call with the ticket link and a one-line throttle recommendation.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AxiomLog streams, queries, dashboards.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.