Create an incident.io follow-up
Use “Create an incident.io follow-up” in Recued. It runs the provider records follow-up creation workflow with approval before changes are made.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (17 steps)
incident_id
trim
Trim whitespace from setting incident id
title
trim
Trim whitespace from setting title
description
trim
Trim whitespace from setting description
assignee_id
trim
Trim whitespace from setting assignee id
assignee_team_id
trim
Trim whitespace from setting assignee team id
external_issue_reference_id
trim
Trim whitespace from setting external issue reference id
follow_up_category_id
trim
Trim whitespace from setting follow up category id
follow_up_priority_option_id
trim
Trim whitespace from setting follow up priority option id
has_title
compare
Check if title has data
incident
?
existing_follow_ups
?
teams
?
users
?
skip_create
compare
Check if has title does not equal true
created_follow_up
?
skip: step.skip_create equal true
existing_count
count
Count items in existing follow ups result
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
title
setting
=
labels
setting
=
incidentio
setting
=
assignee id
setting
=
description
setting
=
incident id
setting
=
assignee team id
setting
=
follow up category id
setting
=
external issue reference id
setting
=
follow up priority option id
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.