Approval-gated PagerDuty incident status update for one incident. It reads the incident for context, acknowledges or resolves exactly that incident through recued-core.pagerduty.incident.status.update, and optionally adds one incident note through recued-core.pagerduty.incident.note.create when note text is present. It does not create incidents, bulk update incidents, reassign, escalate, change priority, edit services, or call arbitrary PagerDuty APIs.

How it works 8 steps

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

Process (8 steps)

■ incident_id trim

Trim whitespace from setting incident id

■ from_email trim

Trim whitespace from setting from email

■ note trim

Trim whitespace from setting note

■ has_note compare

Check if note has data

■ incident_before ?

■ status_update ?

■ note_create ?

skip: step.has_note not_equal true

■ card to_summary

Format results as a summary card

Settings 5 configurable

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

note setting =

status setting = acknowledged

pagerduty setting =

from email setting =

incident id setting =