Recued
Menu
← Back to recipes

PagerDuty incident brief

by recued-core v2 11 views

Use “PagerDuty incident brief” in Recued. It provides a read-only review brief for one PagerDuty incident.

How it works 10 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (10 steps)
incident_id trim
Trim whitespace from setting incident id
incident ?
notes_raw ?
service ?
escalation_policy ?
notes default
Apply default
note_count count
Count items in notes
summarize ?
note_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Summarize the PagerDuty incident for customer or system impact, current status, urgency, assignees, linked service, recent notes, blockers, and concrete next steps. Do not invent facts outside the PagerDuty data.
pagerduty setting =
max length setting = 900
incident id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Read your Pagerduty connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

pagerduty pagerdutyincidentnotesservicebriefai-summarypack:pagerduty

Details

10 steps 4 configurable settings recipe_id: incident-brief-pagerduty