Approval-gated Rootly incident status workflow. It reads the target incident and available statuses for context, then performs exactly one caller-selected lifecycle action through recued-core.rootly.incident.mitigate or recued-core.rootly.incident.resolve with an optional Rootly JSON:API message. It does not create incidents, change arbitrary incident fields, create timeline events or action items, mutate alerts, schedules, escalation policies, services, teams, severities, statuses, users, API keys, or arbitrary Rootly API routes.

How it works 10 steps

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

Process (10 steps)

■ incident_key trim

Trim whitespace from setting incident id

■ status_message trim

Trim whitespace from setting message

■ incident_before ?

■ statuses ?

■ should_mitigate compare

Check if setting action equals mitigate

■ should_resolve compare

Check if setting action equals resolve

■ mitigated_incident ?

skip: step.should_mitigate not_equal true

■ resolved_incident ?

skip: step.should_resolve not_equal true

■ status_count count

Count items in statuses result

■ card to_summary

Format results as a summary card

Settings 4 configurable

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

action setting = mitigate

rootly setting =

message setting =

incident id setting =