IT OPS
PagerDuty incident to status-page note + ElevenLabs hotline update
When a PagerDuty incident is triggered, drafts a customer-safe status-page note with OpenAI, posts it to your status webhook.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggeredPagerDuty
- LogicFilter: customer-impacting severity only
- ActionDraft status note + voice script (OpenAI)OpenAI
- ActionSynthesize hotline audio (ElevenLabs)ElevenLabs
- OutputPublish note to status-page webhookHTTP webhook
What it does
Turns a fresh PagerDuty incident into two customer-facing artifacts at once: a written status-page update and a spoken hotline greeting. Operators get a ready-to-publish note instead of scrambling to write one mid-incident.
When to use it
Use it when you run a public status page and a phone hotline, and want the first customer communication to go out within seconds of an alert firing — without leaking internal jargon, hostnames, or root-cause speculation.
How it works
- 1A PagerDuty incident-trigger webhook fires with the incident title, severity, and affected service.
- 2A logic step filters out low-urgency and auto-resolving incidents so only customer-impacting ones proceed.
- 3OpenAI rewrites the internal alert into a calm, jargon-free status note plus a short spoken script, both scoped to what customers can see.
- 4An ElevenLabs action synthesizes the script into an MP3 voice file for the hotline IVR.
- 5The note is posted to your status-page HTTP webhook and the audio URL is delivered as the final output.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ElevenLabsText-to-speech, voice cloning.
- 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.