Skip to content
Recued
Menu
← Back to recipes

Update incident.io incident fields

by recued-core v1

Approval-gated incident.io incident field update workflow. It reads the target incident, severities, and statuses for context, then edits exactly that incident through recued-core.incidentio.incident.edit with a caller-supplied incident patch object and notification flag. It does not create incidents, close incidents through destructive APIs, create actions or follow-ups, mutate schedules, escalations, status pages, settings, API keys, or call arbitrary incident.io APIs.

How it works 6 steps

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

Process (6 steps)
incident_id trim
Trim whitespace from setting incident id
incident_before ?
severities ?
statuses ?
updated_incident ?
card to_summary
Format results as a summary card
Settings 4 configurable

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

incidentio setting =
incident id setting =
incident patch setting = [object Object]
notify incident channel setting = false

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

Tags

incidentio incidentioincident.ioincidentupdateapprovalpack:incidentio

Details

6 steps 4 configurable settings recipe_id: update-incidentio-incident-fields