Recued
Menu
← Back to recipes

Statuspage incident brief

by recued-core v1 10 views

Use “Statuspage incident brief” in Recued. It provides a read-only review brief for one Statuspage incident.

How it works 12 steps

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

Process (12 steps)
page_id trim
Trim whitespace from setting page id
incident_id trim
Trim whitespace from setting incident id
page ?
incident ?
components_raw ?
defaults defaults
Apply defaults
component_count count
Count items in components
update_count count
Count items in updates
summarize ?
update_rows slice
Take a subset of
update_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 6 configurable

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

focus setting = Summarize the Statuspage incident for customer impact, current status, affected components, update history, open questions, and concrete next steps. Do not invent facts outside the Statuspage data.
page id setting =
row limit setting = 10
max length setting = 900
statuspage setting =
incident id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

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 statuspageincidentbriefcomponentsai-summarycustomer-communicationspack:statuspage

Details

12 steps 6 configurable settings recipe_id: incident-brief-statuspage