Recued
Menu
← Back to recipes

incident.io follow-up triage brief

by recued-core v1 9 views

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 ?
skip: step.has_incident not_equal true
follow_ups_raw ?
actions_raw ?
teams_raw ?
users_raw ?
defaults defaults
Apply defaults
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 =

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 Incidentio connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

incidentio incidentioincident.iofollow-upsactionstriageai-summarypack:incidentio

Details

17 steps 6 configurable settings recipe_id: follow-up-triage-brief-incidentio