IT OPS
Turn a PagerDuty incident into a Notion status-update draft
On a new high-urgency PagerDuty incident, this writes a customer-facing status update as a draft row in a Notion publish queue with severity and impact pre-filled for review.
How it runs
The automated pipeline, trigger to output.
- TriggerNew PagerDuty incident triggeredPagerDuty
- LogicBranch on incident urgency
- ActionGenerate customer-friendly summary + severityOpenAI
- OutputCreate Draft row in Notion publish queueNotion
What it does
It watches PagerDuty for newly triggered incidents and creates a ready-to-review public status update inside a Notion database that acts as your publish queue. Each entry includes a plain-language summary, a proposed customer-facing severity, the affected service, and a draft status (Investigating / Identified / Monitoring). Nothing is public until a teammate flips the row to Approved.
When to use it
Use it when PagerDuty is your source of truth for incidents and your comms team manages public updates in Notion. It removes the lag between an engineer getting paged and a draft being ready for the comms owner to polish and publish.
How it works
- 1PagerDuty triggers a new incident and fires the workflow.
- 2A logic step branches on urgency — only high-urgency incidents create a public draft; low-urgency ones are skipped.
- 3An LLM step maps the internal incident title and service to a customer-friendly summary and a suggested public severity.
- 4A Notion row is created in the status-update queue with state "Draft — needs approval," linking back to the PagerDuty incident for the comms owner.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
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.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
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.