IT OPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly scheduled reliability review
- ActionPull recent work orders from Mondaymonday.com
- ActionQuery telemetry trends from BigQueryBigQuery
- LogicForm root-cause hypothesis and fix
- OutputFile triaged Linear engineering ticketLinear
What it does
This workflow moves past one-off alerts to find the assets that keep breaking. On a schedule, an agent pulls recent facilities work orders from Monday and correlates them with raw telemetry trends in BigQuery to spot units with repeating fault patterns. For each chronic offender it drafts a root-cause hypothesis and a recommended remediation, then opens a triaged Linear ticket so engineering can plan a real fix rather than another patch.
When to use it
Use it when the same air handler, pump, or panel generates work order after work order and nobody has stepped back to ask why. Good for reliability reviews and capital-planning input.
How it works
- 1A weekly schedule starts the investigation.
- 2The agent reads recent work orders from Monday and groups them by asset.
- 3The agent queries BigQuery telemetry to confirm and characterize each recurring fault.
- 4It reasons over the combined evidence to form a root-cause hypothesis and recommended fix.
- 5A triaged Linear ticket is filed with the asset, evidence, and recommendation.
Set it up
What you configure once, before turning it on.
- 1Connect monday.comVisual work management for teams.
- 2Connect BigQueryDatasets, queries, schemas.
- 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 IT Ops workflows
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.
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.