Recued
Menu
← Back to recipes

Update Rootly incident status

by recued-core v1 16 views

Use “Update Rootly incident status” in Recued. It runs the Rootly incident status workflow with approval before changes are made.

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 =

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 Rootly connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.typedata.attributes

About

Tags

rootly rootlyincidentstatusmitigateresolveapprovalpack:rootly

Details

10 steps 4 configurable settings recipe_id: update-incident-status-rootly