Name: Create an incident.io incident intake
Author: recued-core

Create an incident.io incident intake

by recued-core v1

Approval-gated incident.io incident creation workflow. It reads identity, severities, incident statuses, users, teams, and recent incidents for context, then creates exactly one incident through recued-core.incidentio.incident.create with caller-supplied idempotency key, visibility, name, summary, severity ID, status ID, incident type ID, mode, and optional custom fields. It does not edit existing incidents, create actions or follow-ups, mutate schedules, escalations, status pages, settings, API keys, or call arbitrary incident.io APIs.

How it works 16 steps

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 10 configurable

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.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Incidentio connection

Declared by the recipe — Recued grants these at install, where you review them before approving.

About

recued-core

Details

16 steps 10 configurable settings recipe_id: create-incidentio-incident-intake