DEVOPS
Open a Linear cost-RCA issue when a spend anomaly pages PagerDuty
When a cost-anomaly alert triggers a PagerDuty incident, this workflow gathers the offending service, recent deploys, and the cost delta.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty cost-anomaly incident createdPagerDuty
- LogicExtract affected service and anomaly window
- ActionFetch recent deploys and PRs for the serviceGitHub
- LogicAssemble RCA draft and resolve owning team
- OutputCreate assigned cost-RCA issue in LinearLinear
What it does
Converts a cost-driven PagerDuty incident into a tracked remediation item. It pulls the incident's service context, fetches the recent GitHub deploys for that service, computes the suspected over-spend, and creates a Linear issue pre-populated with the timeline, suspect commits, and an owner.
When to use it
Use it when cost anomalies need to be tracked to resolution rather than just acknowledged in chat. Good for teams that run cost monitors through PagerDuty and manage engineering work in Linear.
How it works
- 1PagerDuty triggers the workflow when a cost-anomaly incident is created.
- 2The flow extracts the affected service and anomaly window from the incident payload.
- 3It queries GitHub for deploys and merged PRs to that service inside the window.
- 4A logic step assembles a root-cause draft: timeline, candidate PRs, and estimated dollar impact.
- 5It resolves the owning team from the service-to-team map.
- 6A Linear issue is created with the draft, labeled cost-rca, and assigned to that team's lead.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.