Recued
Menu
← Back to recipes

Rootly incident brief

by recued-core v1 13 views

Use “Rootly incident brief” in Recued. It provides a read-only incident command brief for one Rootly incident.

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
incident ?
timeline_raw ?
action_items_raw ?
services_raw ?
teams_raw ?
users_raw ?
defaults defaults
Apply defaults
timeline_count count
Count items in timeline
action_item_count count
Count items in action items
summarize ?
timeline_rows slice
Take a subset of
action_item_rows slice
Take a subset of
timeline_table to_table
Format results as a data table
action_item_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 5 configurable

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

focus setting = Summarize the Rootly incident for current status, severity, impact, ownership, recent timeline signal, open action items, escalation risk, and concrete next steps. Do not invent facts outside the Rootly data.
rootly setting =
row limit setting = 12
max length setting = 900
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.

About

Tags

rootly rootlyincidentbrieftimelineaction-itemsai-summarypack:rootly

Details

16 steps 5 configurable settings recipe_id: incident-brief-rootly