IT OPS
Cloudflare 5xx surge to auto-published degraded-service banner
Watches Cloudflare for a surge in 5xx responses and, when origin errors confirm a real outage, writes and auto-publishes a degraded-service banner to your status page…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled poll of Cloudflare 5xx error rateCloudflare
- LogicConfirm outage: edge errors AND Sentry server errorsSentry
- ActionWrite degraded-service banner with rolling ETAOpenAI
- OutputAuto-publish banner to status pageHTTP webhook
- ActionNotify team that banner is liveSlack
What it does
Detects an edge-level outage from Cloudflare analytics and publishes a customer-facing degraded-service banner without waiting for a human, because every minute of silence during a confirmed outage costs trust. It cross-checks Sentry to avoid false alarms from a single bad deploy.
When to use it
Use it for high-traffic services where a confirmed 5xx surge should immediately show a banner. Best when you accept fully automated publishing for major-severity events and want the message generated, not templated.
How it works
- 1A schedule polls Cloudflare for the 5xx error rate over the last few minutes.
- 2A logic step confirms the surge is real by requiring both an elevated edge error rate and corroborating Sentry server errors.
- 3An OpenAI step writes a short degraded-service banner with an honest rolling ETA.
- 4The banner is auto-published to the status page via an HTTP webhook.
- 5A Slack message notifies the team that an automated banner went live.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect SentryErrors, performance, releases.
- 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.