IT OPS
Edge Box Recovery Auto-Resolve and Thread Close
When a previously-silent edge box resumes sending heartbeats, this resolves its PagerDuty incident, posts an all-clear to the Discord triage thread, and closes the incident record.
How it runs
The automated pipeline, trigger to output.
- TriggerHeartbeat arrives from a down deviceHTTP webhook
- LogicConfirm open incident and compute downtime
- ActionResolve matching PagerDuty incidentPagerDuty
- OutputPost all-clear and archive Discord threadDiscord
- ActionClose incident row in PostgresPostgres
What it does
Closes the loop on an outage. The moment a device that was flagged down sends a fresh heartbeat, the workflow computes total downtime, resolves any open PagerDuty incident, posts a recovery summary to the Discord triage thread, and archives it so channels don't fill with stale threads.
When to use it
Use it alongside the silence and escalation workflows so recoveries are handled automatically. It guarantees on-call never has to manually close a thread or ack a resolved page, and it leaves a clean downtime record for SLA reporting.
How it works
- 1A heartbeat webhook arrives from a device currently marked down.
- 2A logic step confirms the device had an open incident and computes total downtime from first-missed to now.
- 3An action resolves the matching PagerDuty incident.
- 4The workflow posts an all-clear with the downtime figure to the device's Discord triage thread and archives it.
- 5An action closes the incident row in Postgres, recording the resolution time for reporting.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect DiscordCommunity channels + voice + bots.
- 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
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.