IT OPS
Emergency Maintenance Escalation to On-Call
Classifies severity from a maintenance photo and, only for emergencies like floods or electrical hazards.
How it runs
The automated pipeline, trigger to output.
- TriggerMaintenance request received via webhookHTTP webhook
- ActionAnalyze photo for hazards and severityOpenAI
- LogicBranch on emergency severity threshold
- ActionPage on-call manager for emergenciesPagerDuty
- OutputPost routine issues to facilities SlackSlack
What it does
Acts as a safety net for genuine emergencies. It reads the photo, and when the damage is hazardous (flooding, exposed wiring, gas, structural), it pages the on-call manager through PagerDuty instead of letting the request sit in a queue.
When to use it
Use this when slow response to a true emergency causes real damage or liability, but you do not want every minor request waking up on-call staff. The flow draws a hard line between emergency and routine.
How it works
- 1A webhook receives the request payload with a photo and location.
- 2The photo is analyzed for hazard signals and an overall severity score.
- 3A logic branch checks whether severity crosses the emergency threshold.
- 4If it is an emergency, a high-urgency PagerDuty incident is triggered with the photo, location, and hazard summary for the on-call manager.
- 5If routine, the request is posted to the standard facilities Slack channel for normal scheduling.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.