Read-only review brief for one PagerDuty incident. It reads the incident, incident notes, linked service, and linked escalation policy through recued-core.pagerduty, then asks the AI summarizer for impact, current state, owners, blockers, and next steps. It never acknowledges, resolves, creates, reassigns, escalates, or mutates PagerDuty records.

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 =