DEVOPS
Page the right stakeholders into the war-room by service tier
After a war-room bridge exists, this workflow looks up the affected service's tier and pages the matching escalation group.
How it runs
The automated pipeline, trigger to output.
- TriggerIncident webhook with bridge linkHTTP webhook
- ActionResolve service tier from catalogAirtable
- LogicBranch by service tier
- ActionEscalate responders in PagerDutyPagerDuty
- ActionNotify engineering in SlackSlack
- OutputPage executives in Teams (Tier-0)Microsoft Teams
What it does
Not every incident needs the VP on the call. This workflow routes the Zoom war-room invite differently based on the affected service's business tier: Tier-0 incidents page both engineering and the executive stakeholder group, while lower tiers stay scoped to the responding team.
When to use it
Use it when your war-room already has a bridge link (passed in via webhook) and you need disciplined, tier-aware paging so leadership is looped in for customer-facing outages but not for internal blips.
How it works
- 1A webhook receives the incident payload including the affected service and existing Zoom link.
- 2A lookup against your service catalog in Airtable resolves the service's tier and owning team.
- 3A branch decides the audience: Tier-0 pages everyone, Tier-1/2 pages engineering only.
- 4PagerDuty escalates to the on-call responders for that service.
- 5Slack notifies the engineering channel with the bridge link.
- 6For Tier-0, Microsoft Teams posts an executive-facing summary with the join link to the leadership channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AirtableBases, tables, views, automations.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Connect Microsoft TeamsChannels, chats, files.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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.