Starts
24 Oct 2026 · 02:00 UTC
24 Oct 2026 · 02:00 UTC
Ends
24 Oct 2026 · 02:30 UTC
24 Oct 2026 · 02:30 UTC
Affected service
Order history
Order history
Owner
Platform operations
Platform operations
Incidents and operations / BLOCK KIT JSON
Communicate a maintenance window with exact times, affected services, and expected customer impact.
Blank optional fields are omitted. Fallback text updates with your fields.
Approximate Slack rendering. Buttons are visual previews; no actions are sent.
Local validation checks the supported schema. It does not guarantee Slack API acceptance.
Manual editing and validation run in your browser. Opening Slack’s Builder shares the message with Slack.
Scheduled maintenance · Database upgrade Order history will be read-only during this window. Checkout and payment processing will remain available. No customer action is required. Starts: 24 Oct 2026 · 02:00 UTC Ends: 24 Oct 2026 · 02:30 UTC Affected service: Order history Owner: Platform operations A completion update will follow after verification. Maintenance details: https://example.com/status/maintenance-42
Download the payload or use this command in your own terminal. Replace the placeholder URL with your Slack incoming webhook. Keep the real URL secret. This tool never sends a Slack message.
curl --request POST \
--header 'Content-Type: application/json' \
--data-binary @- \
'https://hooks.slack.com/services/YOUR/WEBHOOK/URL' <<'SLACK_MESSAGE_JSON'
{
"text": "Scheduled maintenance · Database upgrade\nOrder history will be read-only during this window. Checkout and payment processing will remain available. No customer action is required.\nStarts: 24 Oct 2026 · 02:00 UTC\nEnds: 24 Oct 2026 · 02:30 UTC\nAffected service: Order history\nOwner: Platform operations\nA completion update will follow after verification.\nMaintenance details: https://example.com/status/maintenance-42",
"blocks": [
{
"type": "header",
"text": {
"type": "plain_text",
"text": "Scheduled maintenance · Database upgrade"
}
},
{
"type": "section",
"fields": [
{
"type": "mrkdwn",
"text": "*Starts*\n24 Oct 2026 · 02:00 UTC"
},
{
"type": "mrkdwn",
"text": "*Ends*\n24 Oct 2026 · 02:30 UTC"
},
{
"type": "mrkdwn",
"text": "*Affected service*\nOrder history"
},
{
"type": "mrkdwn",
"text": "*Owner*\nPlatform operations"
}
]
},
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "Order history will be read-only during this window. Checkout and payment processing will remain available. No customer action is required."
}
},
{
"type": "context",
"elements": [
{
"type": "mrkdwn",
"text": "A completion update will follow after verification."
}
]
},
{
"type": "divider"
},
{
"type": "actions",
"elements": [
{
"type": "button",
"text": {
"type": "plain_text",
"text": "Maintenance details"
},
"action_id": "status-url",
"url": "https://example.com/status/maintenance-42"
}
]
}
]
}
SLACK_MESSAGE_JSONAnnounce planned work before it happens so support and operations can prepare. A clear time zone and an explicit impact statement prevent readers from confusing planned downtime with an active incident.
Specify start and end times in a named time zone, preferably UTC. Explain whether users need to take action and what happens if the work overruns. Use the completed variant only after service checks pass.
Included variants: scheduled, completed. Switch variants in the editor; all versions stay on this page.
Schedule the announcement from your maintenance process. Update the status page independently; generating or posting this message does not schedule infrastructure changes.
To post this JSON, create a Slack app with an incoming webhook for your channel, or use chat.postMessage with the appropriate bot token and permissions. Keep credentials on your server.
For buttons, enable Interactivity and handle Slack’s interaction requests, including URL buttons. Acknowledge requests promptly. This preview does not execute actions, authorize users, or save decisions.
Use the top-level fallback text for notifications and accessibility. Test your final payload in Slack; local validation covers the declared subset, and visual details vary by client.
Slack interaction setup ↗