Read-only follow-up triage brief for one incident.io incident or assignee team. It reads follow-ups, actions, teams, users, and optional incident context through recued-core.incidentio, then asks the AI summarizer for owners, blocked work, aging risk, duplicate work, and next steps. It never creates, updates, completes, deletes, or exports follow-ups, actions, incidents, schedules, escalations, settings, or arbitrary incident.io API routes.

How it works 20 steps

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

Process (20 steps)

■ incident_id trim

Trim whitespace from setting incident id

■ assignee_team_id trim

Trim whitespace from setting assignee team id

■ has_incident compare

Check if incident id has data

■ incident ?

skip: step.has_incident not_equal true

■ follow_ups_raw ?

■ actions_raw ?

■ teams_raw ?

■ users_raw ?

■ follow_ups default

Apply default

■ actions default

Apply default

■ teams default

Apply default

■ users default

Apply default

■ follow_up_count count

Count items in follow ups

■ action_count count

Count items in actions

■ summarize ?

■ follow_up_rows slice

Take a subset of

■ action_rows slice

Take a subset of

■ follow_up_table to_table

Format results as a data table

■ action_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 6 configurable

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

focus setting = Summarize follow-up triage for ownership, overdue risk, duplicate work, missing assignees, unresolved action overlap, and concrete next steps. Do not invent facts outside incident.io data.

row limit setting = 15

incidentio setting =

max length setting = 900

incident id setting =

assignee team id setting =