DEVOPS
Axiom Budget-Breach Linear Ticket Opener
On an Axiom budget-burn alert webhook, enriches the alert with the offending dataset and growth delta.
How it runs
The automated pipeline, trigger to output.
- TriggerAxiom budget-burn alert webhookHTTP webhook
- ActionFetch breaching dataset + growth deltaAxiom
- LogicSearch Linear for existing open ticketLinear
- LogicBranch: dedupe vs. create new
- ActionCreate or comment on Linear issueLinear
- OutputConfirm ticket in SlackSlack
What it does
When Axiom fires a budget-burn monitor alert, this workflow turns it into an actionable, owned engineering ticket. It pulls the dataset that breached, computes the week-over-week growth delta, finds the owning team, and creates a Linear issue — reusing an existing open ticket for the same dataset instead of spawning duplicates.
When to use it
Use it when overages need an accountable owner and a paper trail, not just a Slack ping that scrolls away. Good for teams that triage cost regressions in their normal issue queue.
How it works
- 1An Axiom monitor posts a budget-burn alert to the webhook trigger.
- 2Query Axiom for the breaching dataset's volume and its 7-day growth delta.
- 3A logic step searches Linear for an open ticket already tagged with that dataset.
- 4Branch: if one exists, add a comment with fresh numbers; otherwise create a new issue routed to the owning team with the evidence in the body.
- 5Confirm the created or updated ticket back in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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 DevOps workflows
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.