IT OPS
HVAC Anomaly Detection to Severity-Routed Work Orders
Ingests building HVAC telemetry via webhook, flags out-of-band temperature, pressure, or runtime readings.
How it runs
The automated pipeline, trigger to output.
- TriggerReceive HVAC telemetry payloadHTTP webhook
- LogicClassify reading: normal / warning / critical
- LogicDrop normal readings, continue anomalies
- ActionCreate severity-tagged Monday work ordermonday.com
- OutputAlert facilities on-call in SlackSlack
What it does
This workflow turns raw HVAC sensor readings into actionable maintenance work. It receives telemetry pushed from your building management system, evaluates each reading against your thresholds for supply temperature, static pressure, and compressor runtime, and decides whether a reading is normal, a warning, or critical. Anomalies become Monday work orders tagged with the right severity, and the on-call team gets a Slack alert so nothing waits in a queue unseen.
When to use it
Use it when your BMS or sensor gateway can POST readings but has no logic to escalate them — you want a single place that decides what is worth a technician's time and who gets paged for what. Ideal for facilities teams running multiple rooftop units or air handlers across one or more sites.
How it works
- 1The webhook receives a telemetry payload (unit ID, metric, value, timestamp).
- 2A logic step compares each metric to its configured normal band and classifies the reading as normal, warning, or critical.
- 3Normal readings stop here; warnings and criticals continue.
- 4A Monday item is created in the maintenance board with severity, unit, and the offending metric.
- 5A Slack message posts to the facilities on-call channel with the work order link and severity.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect monday.comVisual work management for teams.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 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.
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
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.