IT OPS
Sustained Edge Silence Escalation to PagerDuty
Distinguishes a brief blip from a real outage: only when an edge box stays silent past a grace threshold does it page on-call via PagerDuty and link the existing Discord triage…
How it runs
The automated pipeline, trigger to output.
- TriggerEvery two minutes: re-check late devices
- ActionRead silence duration for late devicesPostgres
- LogicKeep only devices past grace, not yet paged
- ActionOpen PagerDuty incident scaled by durationPagerDuty
- OutputPost PagerDuty link into Discord triage threadDiscord
- ActionMark device escalated in PostgresPostgres
What it does
Guards against alert fatigue by waiting out transient drops. It re-checks a device that missed a beat and, only if it remains silent beyond a configurable grace period, opens a PagerDuty incident with the site, device, and duration of silence — then drops the PagerDuty link into the device's Discord triage thread so chat and paging stay connected.
When to use it
Use it when a momentary network hiccup shouldn't wake anyone, but a genuinely down site must page immediately. It sits one tier above the triage-thread workflow, escalating only confirmed sustained outages.
How it works
- 1A scheduled check runs every two minutes against the heartbeat ledger.
- 2An action pulls devices flagged `late` and reads how long each has been silent.
- 3A logic step keeps only devices past the grace threshold and not already paged.
- 4An action triggers a PagerDuty incident with severity scaled to the silence duration.
- 5The workflow posts the PagerDuty incident link into the device's open Discord thread and marks it escalated in Postgres.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect DiscordCommunity channels + voice + bots.
- 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.
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.
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.
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.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
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.