IT OPS
Incident Resolution All-Clear Publisher
When Sentry marks an issue as resolved, drafts a friendly all-clear update, confirms the error rate has actually dropped via Cloudflare.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue marked resolvedSentry
- ActionCheck edge error rate at baselineCloudflare
- LogicHold if errors still elevated
- ActionDraft plain-language all-clearOpenAI
- OutputPublish resolution + notify SlackHTTP webhook
What it does
Closes the loop on an incident. Many teams publish the outage but forget the all-clear, leaving a stale red banner. This drafts a plain-language resolution note, verifies recovery against real traffic data before declaring victory, and updates the public page.
When to use it
Use it when incidents get opened on your status page but resolutions lag or get skipped. Good for teams that want the all-clear to be both timely and trustworthy, backed by an actual recovery signal rather than a hopeful guess.
How it works
- 1A Sentry webhook fires when the issue status changes to resolved.
- 2Cloudflare analytics are checked to confirm the error rate at the edge has genuinely returned to baseline.
- 3A logic gate holds the update if errors are still elevated, avoiding a premature all-clear.
- 4OpenAI drafts a warm, plain-language resolution message referencing the original incident.
- 5The resolution publishes to the status page via HTTP webhook and a wrap-up note is posted to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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.