Create a Rootly incident intake
Use “Create a Rootly incident intake” in Recued. It runs the Rootly incident creation workflow with approval before changes are made.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (19 steps)
incident_title
trim
Trim whitespace from setting title
incident_summary
trim
Trim whitespace from setting summary
incident_kind
trim
Trim whitespace from setting kind
incident_severity_id
trim
Trim whitespace from setting severity id
incident_status
trim
Trim whitespace from setting status
has_title
compare
Check if incident title has data
current_user
?
severities
?
services
?
teams
?
recent_incidents
?
skip_create
compare
Check if has title does not equal true
created_incident
?
skip: step.skip_create equal true
skipped
compare
Check if skip create equals true
severity_count
count
Count items in severities result
service_count
count
Count items in services result
team_count
count
Count items in teams result
recent_incident_count
count
Count items in recent incidents result
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
kind
setting
=
title
setting
=
labels
setting
=
rootly
setting
=
status
setting
=
private
setting
=
false
summary
setting
=
group ids
setting
=
service ids
setting
=
severity id
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.