Use “Create a Rootly action item” in Recued. It runs the Rootly incident action-item creation workflow with approval before changes are made.

How it works 16 steps

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

Process (16 steps)

■ incident_key trim

Trim whitespace from setting incident id

■ action_summary trim

Trim whitespace from setting summary

■ action_description trim

Trim whitespace from setting description

■ assignee_user_id trim

Trim whitespace from setting assigned to user id

■ action_priority trim

Trim whitespace from setting priority

■ action_status trim

Trim whitespace from setting status

■ action_due_date trim

Trim whitespace from setting due date

■ has_summary compare

Check if action summary has data

◆ incident recued-core.rootly.incident.read

Read incident on rootly

◆ existing_action_items recued-core.rootly.action_item.search

Search action item on rootly

◆ users recued-core.rootly.user.search

Search user on rootly

■ skip_create compare

Check if has summary does not equal true

◆ created_action_item recued-core.rootly.action_item.incident.create

Create action item incident on rootly

skip: step.skip_create equal true

■ existing_count count

Count items in existing action items result

■ user_count count

Count items in users result

■ card to_summary

Format results as a summary card

▼

Output

summary card

Settings 8 configurable

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

status setting =

summary setting =

due date setting =

priority setting =

description setting =

incident id setting =

assigned to user id setting =

assigned to group ids setting =