Name: Create a Rootly incident intake
Author: recued-core

Create a Rootly incident intake

by recued-core v1

Approval-gated Rootly incident creation workflow. It reads the current user, severities, services, teams, and recent incidents for context, validates the caller-supplied title, then creates exactly one incident through recued-core.rootly.incident.create using Rootly JSON:API fields for title, summary, kind, privacy, severity, services, teams, labels, and status. It does not edit existing incidents, create action items, mutate alerts, schedules, escalation policies, services, teams, severities, statuses, users, API keys, or arbitrary Rootly API routes.

How it works 19 steps

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 10 configurable

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.

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

19 steps 10 configurable settings recipe_id: create-rootly-incident-intake