Statuspage incident brief
Use “Statuspage incident brief” in Recued. It provides a read-only review brief for one Statuspage incident.
How it works
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
recued-core.statuspage.page.read
Read page on statuspage
incident
recued-core.statuspage.incident.read
Read incident on statuspage
components_raw
recued-core.statuspage.component.search
Search component on statuspage
defaults
defaults
Apply defaults
component_count
count
Count items in components
update_count
count
Count items in updates
summarize
core.ai.summarize
AI generates a concise summary
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
▼
Output
summary
card
table
update_table
Settings
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
incident id
setting
=
Uses (4 operations)
Pack operation
Read page on statuspage
recued-core.statuspage.page.read
Pack operation
Read incident on statuspage
recued-core.statuspage.incident.read
Pack operation
Search component on statuspage
recued-core.statuspage.component.search
AI models
AI generates a concise summary
core.ai.summarize
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
Permissions it requires
Declared by the recipe — Recued grants these at install, where you review them before approving.What it's allowed to do
Read
AI models
core.ai.summarize
read-only
3 more aren't listed here. You'll see them at install.