Name: Create a Rootly action item
Author: recued-core

Create a Rootly action item

by recued-core v1

Approval-gated Rootly incident action-item creation workflow. It reads the target incident, existing action items, and users for context, validates the caller-supplied summary, then creates exactly one incident action item through recued-core.rootly.action_item.incident.create with Rootly JSON:API fields for summary, description, assignee user, assignee teams, priority, status, and due date. It does not edit incidents, update or delete existing action items, mutate alerts, schedules, escalation policies, services, teams, users, API keys, or arbitrary Rootly API routes.

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 ?

■ existing_action_items ?

■ users ?

■ skip_create compare

Check if has summary does not equal true

■ created_action_item ?

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

Settings 9 configurable

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

rootly setting =

status setting =

summary setting =

due date setting =

priority setting =

description setting =

incident id setting =

assigned to user id setting =

assigned to group ids setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

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

recued-core

Details

16 steps 9 configurable settings recipe_id: create-rootly-action-item