Approval-gated incident.io action creation workflow. It reads the target incident, existing actions, and users for context, then creates exactly one action through recued-core.incidentio.action.create with caller-supplied description and optional assignee. It does not edit incidents, update or delete existing actions, create follow-ups, mutate schedules, escalations, status pages, settings, API keys, or call arbitrary incident.io APIs.

How it works 11 steps

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

Process (11 steps)

■ incident_id trim

Trim whitespace from setting incident id

■ description trim

Trim whitespace from setting description

■ assignee_id trim

Trim whitespace from setting assignee id

■ has_description compare

Check if description has data

■ incident ?

■ existing_actions ?

■ users ?

■ skip_create compare

Check if has description does not equal true

■ created_action ?

skip: step.skip_create equal true

■ existing_count count

Count items in existing actions result

■ card to_summary

Format results as a summary card

Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

incidentio setting =

assignee id setting =

description setting =

incident id setting =