IT OPS
Refresh status-page ETA when PagerDuty escalates an incident
When a PagerDuty incident escalates or its priority changes, regenerates an honest.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident escalation or priority changePagerDuty
- LogicConfirm incident open and change is an escalation
- ActionWrite revised update with conservative ETAOpenAI
- OutputPost refreshed ETA to status pageHTTP webhook
- ActionRecord new ETA in SlackSlack
What it does
Keeps the public ETA honest as an incident worsens. The first estimate is almost always optimistic; when PagerDuty escalates an incident or bumps its priority, this rewrites the customer message with a realistic revised ETA and an acknowledgment that the team is still on it.
When to use it
Use it when a single initial estimate is not enough and prolonged incidents need visible, trustworthy updates. Ideal for teams already running incidents through PagerDuty who want status-page ETAs to track reality.
How it works
- 1PagerDuty fires on an escalation or priority change for an active incident.
- 2A logic step confirms the incident is still open and the change is an escalation, not a downgrade or resolution.
- 3An OpenAI step writes a revised update with a new, deliberately conservative ETA referencing how long the incident has run.
- 4The refreshed update is posted to the status page via an HTTP webhook.
- 5A Slack message records the new ETA for the on-call team.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 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.