IT OPS
Patch escalation ladder to owner then manager
Tracks how long each laptop has been overdue and escalates: a polite Outlook email to the owner first, then a CC to their manager if it stays unpatched past a second threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery overdue devices + managerPostgres
- LogicBranch by escalation tier
- ActionBuild tier-appropriate email
- OutputSend Outlook email (CC manager on tier 2)Outlook
- ActionLog escalation to audit tablePostgres
What it does
Applies a tiered escalation policy to overdue laptops. Devices in the first overdue tier get a reminder email to the owner. Devices that cross a harder deadline get a second email that also copies the owner's manager, framed as a compliance risk. Compliant or recently remediated devices are skipped, so nobody gets nagged after they fix it.
When to use it
Use this when a single nudge is not enough and you need a documented escalation trail for audit or security reviews. Good for regulated fleets where unpatched endpoints must be tracked to resolution.
How it works
- 1A daily schedule triggers the run.
- 2A Postgres query returns overdue devices with owner email, manager email, and days overdue.
- 3A logic branch sorts each device into tier one (owner-only) or tier two (owner plus manager) based on days overdue.
- 4An action builds the tier-appropriate message including the self-service fix link.
- 5The output step sends each email through Outlook, copying the manager on tier-two cases.
- 6The send and tier are written back to Postgres for the audit trail.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect OutlookMail, calendar, contacts.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
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.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
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.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
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.
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.