IT OPS
PagerDuty resolve to status resolution + recap
When a PagerDuty incident resolves, this drafts the closing status-page update plus a short customer-facing recap, gets it approved in Slack, and publishes the resolution.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident resolvedPagerDuty
- LogicConfirm public update exists
- ActionDraft resolution and recapOpenAI
- ActionPost draft to Slack for approvalSlack
- OutputPublish resolution to status pageHTTP webhook
What it does
When a PagerDuty incident moves to resolved, it drafts the final status-page entry that marks the issue resolved and a brief, blameless recap of what happened and what was done. A human approves in Slack, then the resolution publishes.
When to use it
Use it to close the loop on incidents that were already posted publicly. Operators often nail the opening update and forget a clean resolution; this guarantees customers get a tidy close and a short recap every time.
How it works
- 1PagerDuty fires its incident.resolved webhook into Hive.
- 2A logic step confirms a public status update was opened for this incident; internal-only incidents stop here.
- 3An OpenAI step drafts a resolved-status entry plus a two-to-three sentence customer recap.
- 4The draft posts to Slack for approval.
- 5On approval, the resolution and recap publish to the status page via HTTP webhook.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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.