Create an incident.io incident intake
Use “Create an incident.io incident intake” in Recued. It runs the provider records incident creation workflow with approval before changes are made.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (16 steps)
idempotency_key
trim
Trim whitespace from setting idempotency key
name
trim
Trim whitespace from setting name
summary
trim
Trim whitespace from setting summary
severity_id
trim
Trim whitespace from setting severity id
incident_status_id
trim
Trim whitespace from setting incident status id
incident_type_id
trim
Trim whitespace from setting incident type id
has_key
compare
Check if idempotency key has data
has_name
compare
Check if name has data
identity
?
severities
?
statuses
?
recent_incidents
?
skip_create
any
Check if any of the conditions are true
created_incident
?
skip: step.skip_create equal true
skipped
compare
Check if skip create equals true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
mode
setting
=
standard
name
setting
=
summary
setting
=
incidentio
setting
=
visibility
setting
=
public
severity id
setting
=
idempotency key
setting
=
incident type id
setting
=
incident status id
setting
=
custom field entries
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.