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

How it works 19 steps

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

Process (19 steps)

■ incident_id trim

Trim whitespace from setting incident id

■ incident ?

■ updates_raw ?

■ actions_raw ?

■ follow_ups_raw ?

■ users_raw ?

■ teams_raw ?

■ defaults defaults

Apply defaults

■ update_count count

Count items in updates

■ action_count count

Count items in actions

■ follow_up_count count

Count items in follow ups

■ summarize ?

■ update_rows slice

Take a subset of

■ action_rows slice

Take a subset of

■ follow_up_rows slice

Take a subset of

■ update_table to_table

Format results as a data table

■ action_table to_table

Format results as a data table

■ follow_up_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 incident.io incident for current status, severity, ownership, recent updates, open actions, follow-ups, escalation risk, and concrete next steps. Do not invent facts outside the incident.io data.

row limit setting = 12

incidentio setting =

max length setting = 900

incident id setting =