IT OPS
Incident-Resolved Trigger Recap to Linear
When a PagerDuty incident is resolved, gathers its timeline, linked Datadog graphs, and related Sentry issue.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident resolved webhookPagerDuty
- ActionFetch incident timeline + responder notesPagerDuty
- ActionPull related Datadog metric windowDatadog
- ActionLook up linked Sentry issueSentry
- LogicDecide severity and follow-up necessity
- OutputCreate tracked follow-up issue in LinearLinear
What it does
The moment a PagerDuty incident closes, this captures the full story while it's fresh — the timeline, the responder notes, the Datadog metric snapshot that triggered it, and the Sentry issue it correlated to — and turns it into a follow-up ticket in Linear. The handoff value is that resolved-but-not-root-caused incidents become tracked work instead of fading memory.
When to use it
Use it when incidents get mitigated under pressure but the real fix is deferred, and you want each resolution to automatically generate a triaged follow-up the next shift or owning team can pick up.
How it works
- 1A PagerDuty webhook fires on incident resolution.
- 2Fetch the full incident timeline, responders, and notes from PagerDuty.
- 3Pull the related Datadog monitor's recent metric window for context.
- 4Look up any Sentry issue linked to the incident.
- 5A logic step decides severity and whether a follow-up is warranted (skips low-priority auto-resolves).
- 6Create a Linear issue with the recap, labels, and links as a tracked handoff item.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect SentryErrors, performance, releases.
- 4Connect LinearIssues, projects, cycles, triage.
- 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
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.