incident.io incident operations digest
Use “incident.io incident operations digest” in Recued. It provides a scheduled, read-only digest for provider records operations.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (24 steps)
identity
?
incidents_raw
?
actions_raw
?
follow_ups_raw
?
schedules_raw
?
escalations_raw
?
defaults
defaults
Apply defaults
incident_count
count
Count items in incidents
action_count
count
Count items in actions
follow_up_count
count
Count items in follow ups
escalation_count
count
Count items in escalations
has_attention_items
any
Check if any of the conditions are true
notify_enabled
compare
Check if setting notify when attention needed equals true
should_notify
all
Check if all conditions are true
notify
?
skip: step.should_notify not_equal true
incident_rows
slice
Take a subset of
action_rows
slice
Take a subset of
follow_up_rows
slice
Take a subset of
escalation_rows
slice
Take a subset of
incident_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
escalation_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
channels
setting
=
in_app
end hour
setting
=
10
weekdays
setting
=
1,2,3,4,5
page size
setting
=
25
row limit
setting
=
10
incidentio
setting
=
start hour
setting
=
8
notify when attention needed
setting
=
true
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.