IT OPS
Severity-Tiered Incident Router
Classifies a Sentry-confirmed incident into a severity tier and routes the right plain-language update to the right place: critical posts to the status page immediately.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry alert receivedSentry
- ActionDraft summary + propose severity tierOpenAI
- LogicBranch by tier: critical/major vs minor
- OutputCritical/major: publish to status pageHTTP webhook
- OutputMinor: hold in Slack for reviewSlack
What it does
Applies a severity policy so that not every incident gets the same treatment. It scores the Sentry issue, picks a tier, and branches: critical and major incidents publish a public status update fast, while minor ones are held in Slack for a human to decide whether customers even need to hear about it.
When to use it
Use it when you over-communicate small blips or under-communicate big ones because everything follows one path. This separates true customer-impacting outages from internal noise and matches your comms urgency to actual impact.
How it works
- 1A Sentry alert delivers the issue, affected release, and event volume.
- 2OpenAI drafts a plain-language summary and proposes a severity tier from the impact signals.
- 3A branch routes by tier: critical or major versus minor.
- 4Critical and major updates publish straight to the status page via HTTP webhook and ping the incident channel in Slack.
- 5Minor incidents are posted to Slack only, with a publish button so a human can escalate if needed.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 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 IT Ops workflows
Recurring Sensor Fault Root-Cause Investigator
On a schedule, an agent reviews recent Monday work orders and BigQuery telemetry to identify equipment with repeating faults, drafts a root-cause hypothesis with a recommended fix.
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Agentic Inactive-Seat Reclamation Review
An agent investigates each idle SaaS seat by correlating SSO login gaps with HR status and ticket history, classifies it as reclaim, hold, or escalate, and drafts a reasoned…
Reconcile SSO logins against expense spend to find unmanaged tools
Joins SSO usage data with expense/payment records in Snowflake to surface tools that are being used but not paid for, or paid for but never logged.
Approved-Seat Deprovision Execution
Fires when an IT approver confirms a seat for removal, then executes deprovisioning via the IdP API and logs the action to an audit table and a Linear cleanup ticket.
HVAC Anomaly Detection to Severity-Routed Work Orders
Ingests building HVAC telemetry via webhook, flags out-of-band temperature, pressure, or runtime readings.
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.