IT OPS
Edge Box Missed Heartbeat to Discord Triage Thread
When a site's edge device stops sending its periodic heartbeat, this opens a dedicated triage thread in Discord with the site's last-known status so on-call can start working…
How it runs
The automated pipeline, trigger to output.
- TriggerEvery minute: scan heartbeat ledger
- ActionQuery Postgres for devices past their check-in windowPostgres
- LogicDrop devices already in an open incident
- ActionRead last-known status row for each silent devicePostgres
- OutputOpen a per-site Discord triage thread with contextDiscord
- ActionRecord open incident back to PostgresPostgres
What it does
Watches the heartbeat ledger for every on-prem edge box and, when a device misses its expected check-in window, spins up a focused Discord triage thread named after the affected site. The thread is pre-loaded with the device's last-seen timestamp, firmware version, and recent status so responders skip the lookup phase.
When to use it
Use it when you run fleets of remote edge boxes (retail, warehouses, clinics) and a silent device means a site is effectively offline. It replaces noisy channel pings with one tidy thread per incident that the whole on-call team can collaborate in.
How it works
- 1A scheduled check fires every minute and queries the Postgres heartbeat table for devices whose `last_seen` is older than their allowed interval.
- 2A logic step filters out devices already in an open incident so threads aren't duplicated.
- 3For each newly-silent device, an action reads its last-known status row (firmware, site, uptime).
- 4The workflow creates a Discord thread titled with the site and device ID, posting the enriched context as the first message.
- 5The new incident is recorded back to Postgres so the dedupe filter stays accurate.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect DiscordCommunity channels + voice + bots.
- 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
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.