Skip to content
Recued
Menu
← Back to recipes

Create a Statuspage incident

by recued-core v1

Approval-gated Statuspage incident creation for one page. It reads the page and components for context, then creates exactly one incident through recued-core.statuspage.incident.create with caller-supplied name, status, impact, message, component IDs, and notification flags. It does not update components outside the incident payload, mutate subscribers, edit page configuration, schedule maintenance, create postmortems, delete records, or call arbitrary Statuspage APIs.

How it works 7 steps

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

Process (7 steps)
page_id trim
Trim whitespace from setting page id
name trim
Trim whitespace from setting name
body trim
Trim whitespace from setting body
page ?
components ?
create ?
card to_summary
Format results as a summary card
Settings 9 configurable

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

body setting =
name setting =
status setting = investigating
page id setting =
statuspage setting =
component ids setting =
impact override setting = minor
deliver notifications setting = true
auto transition to operational state 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 Statuspage connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

statuspage statuspageincidentcreatecustomer-communicationsapprovalpack:statuspage

Details

7 steps 9 configurable settings recipe_id: create-statuspage-incident