Use “incident.io follow-up triage brief” in Recued. It provides a read-only follow-up triage brief for one provider record incident or assignee team.

How it works 17 steps

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

Process (17 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 recued-core.incidentio.incident.read

Read incident on incidentio

skip: step.has_incident not_equal true

◆ follow_ups_raw recued-core.incidentio.follow_up.search

Search follow up on incidentio

◆ actions_raw recued-core.incidentio.action.search

Search action on incidentio

◆ teams_raw recued-core.incidentio.team.search

Search team on incidentio

◆ users_raw recued-core.incidentio.user.search

Search user on incidentio

■ defaults defaults

Apply defaults

■ follow_up_count count

Count items in follow ups

■ action_count count

Count items in actions

✦ summarize core.ai.summarize

AI generates a concise summary

■ 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

▼

Output

summary card

table follow_up_table

table action_table

Settings 5 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

max length setting = 900

incident id setting =

assignee team id setting =