IT OPS
Auto all-clear update when Sentry error rate returns to baseline
Monitors a resolving incident and, once Sentry error volume drops back to baseline and stays there, drafts and posts a friendly resolved update closing out the status-page…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled check of incident issue error rateSentry
- LogicRequire sustained baseline across consecutive checks
- ActionDraft reassuring resolved all-clear messageOpenAI
- OutputPost resolved update and close incidentHTTP webhook
- ActionConfirm auto-close in SlackSlack
What it does
Closes the loop on incidents that humans forget to mark resolved. It watches the error rate of an active incident, waits for a sustained return to baseline, then writes a warm all-clear message and posts the resolved update so the status page never stays red longer than reality.
When to use it
Use it as the companion to any incident-opening workflow. It is for teams whose status pages routinely show stale outages because everyone moved on once the fire was out.
How it works
- 1A schedule checks the error rate for the issue tied to an open incident.
- 2A logic step requires the rate to sit at or below baseline across several consecutive checks before declaring recovery, avoiding premature all-clears during a flapping recovery.
- 3An OpenAI step drafts a brief, reassuring resolved message summarizing impact and duration.
- 4The resolved update is posted to the status page via an HTTP webhook, flipping the incident to resolved.
- 5A Slack note confirms the incident was auto-closed.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
Recurring Sensor Fault Root-Cause Investigator
On a schedule, an agent reviews recent Monday work orders and BigQuery telemetry to identify equipment with repeating faults, drafts a root-cause hypothesis with a recommended fix.
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.
Agentic Inactive-Seat Reclamation Review
An agent investigates each idle SaaS seat by correlating SSO login gaps with HR status and ticket history, classifies it as reclaim, hold, or escalate, and drafts a reasoned…
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.
Approved-Seat Deprovision Execution
Fires when an IT approver confirms a seat for removal, then executes deprovisioning via the IdP API and logs the action to an audit table and a Linear cleanup ticket.
HVAC Anomaly Detection to Severity-Routed Work Orders
Ingests building HVAC telemetry via webhook, flags out-of-band temperature, pressure, or runtime readings.
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.