IT OPS
Edge Heartbeat Webhook Ingest with Silence Flagging
Receives heartbeat POSTs from on-prem edge boxes, records each one to Postgres, and flags the device as healthy or stale so downstream monitors have a single source of truth.
How it runs
The automated pipeline, trigger to output.
- TriggerEdge box POSTs a heartbeatHTTP webhook
- LogicValidate payload and known device ID
- ActionRead previous heartbeat to compute gapPostgres
- LogicSet healthy / late flag from interval
- OutputUpsert normalized heartbeat row to PostgresPostgres
What it does
Provides the inbound endpoint that every edge box pings on its interval. Each POST is validated, timestamped, and written to the heartbeat ledger. The workflow compares the gap since the device's previous beat against its configured interval and stamps a `healthy` or `late` flag, giving the rest of your monitors a clean signal to read.
When to use it
Use it as the foundation under any heartbeat alerting. If your edge fleet phones home over HTTP, this is the front door that normalizes those pings into structured rows other workflows and dashboards can trust.
How it works
- 1An edge box sends an HTTP webhook with its device ID, site, firmware, and timestamp.
- 2A logic step validates the payload and rejects malformed or unknown device IDs.
- 3An action reads the device's previous heartbeat to compute the gap since last contact.
- 4A logic step sets the status flag: `late` if the gap exceeded the interval, else `healthy`.
- 5The normalized heartbeat row, with flag, is upserted into Postgres as the canonical record.
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.
- 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.