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 recued-core.rootly.incident.read

Read incident on rootly

◆ timeline_raw recued-core.rootly.incident_event.search

Search incident event on rootly

◆ action_items_raw recued-core.rootly.action_item.search

Search action item on rootly

◆ services_raw recued-core.rootly.service.search

Search service on rootly

◆ teams_raw recued-core.rootly.team.search

Search team on rootly

◆ users_raw recued-core.rootly.user.search

Search user on rootly

■ defaults defaults

Apply defaults

■ timeline_count count

Count items in timeline

■ action_item_count count

Count items in action items

✦ summarize core.ai.summarize

AI generates a concise summary

■ 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

▼

Output

summary card

table timeline_table

table action_item_table

Settings 4 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.

row limit setting = 12

max length setting = 900

incident id setting =