previewcode
Copy codeInstall command
Search blocks by description or jump to a page.
Incident Update Composer is the internal form an operator uses to post the next public update: an incident header shows INC-2419, a Sev 2 Badge, and the start time, then a status phase RadioGroup (Investigating, Identified, Monitoring, Resolved), a Textarea prefilled with a customer ready message, affected component checkboxes (Webhooks and API checked), and notification channel switches for email, SMS, and Slack with recipient counts. A Save draft and Post update pair closes the panel.
Phases, components, and channels are typed const arrays, so the form maps straight to your incident schema. Helper lines explain that moving to Resolved closes the incident and that every post refreshes the RSS feed and status page.
Reach for this block inside an incident management tool or the admin side of a status page, wired to your incident log and subscriber lists. Point the Post update action at your status page API and the channel switches at your email and SMS providers.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the public incident update form. Other composer shapes:
Tip: keep the helper line about writing for customers, the message field is where an incident becomes trust rather than jargon.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Every block and every tool, for one person.
Pro for every seat, plus what a team needs.
Already on a plan? Log in