Update Rootly incident status
Use “Update Rootly incident status” in Recued. It runs the Rootly incident status workflow with approval before changes are made.
How it works
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
recued-core.rootly.incident.read
Read incident on rootly
statuses
recued-core.rootly.status.search
Search status on rootly
should_mitigate
compare
Check if setting action equals mitigate
should_resolve
compare
Check if setting action equals resolve
mitigated_incident
recued-core.rootly.incident.mitigate
Mitigate incident on rootly
skip: step.should_mitigate not_equal true
resolved_incident
recued-core.rootly.incident.resolve
Resolve incident on rootly
skip: step.should_resolve not_equal true
status_count
count
Count items in statuses result
card
to_summary
Format results as a summary card
▼
Output
summary
card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
action
setting
=
mitigate
message
setting
=
incident id
setting
=
Uses (4 operations)
Pack operation
Read incident on rootly
recued-core.rootly.incident.read
Pack operation
Search status on rootly
recued-core.rootly.status.search
Pack operation
Mitigate incident on rootly
recued-core.rootly.incident.mitigate
Pack operation
Resolve incident on rootly
recued-core.rootly.incident.resolve
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.