Recipe Book
Choose a recipe, then select your language. Every recipe has native code for all ten implementations and an output preview generated from its tested example. Message construction and rendering do not implement callbacks or send Slack requests.
| Recipe | Result |
|---|---|
| Build status notification | Build summary with fields and a footer |
| Approval request with action buttons | Approve/reject buttons with callback identifiers |
| Rich-formatted alert | Styled rich text |
| Confirmation modal | An input view for an interaction trigger |
| Threaded reply | A reply tied to a parent timestamp |
| Ephemeral slash-command response | A response visible to the invoking user |
| Multi-column status report | A compact service table |
| Colored-bar attachment | A legacy colored attachment |
| Preview in Block Kit Builder | A locally generated Builder URL |
| Parse incoming modeled JSON | Checked input or an explicitly scoped adapter |
| Workflow button | A parameterized workflow trigger |
| Typed validation error handling | A categorized validation failure |
| Accordion and pagination | Collapsible detail and paged content |
| Metadata and safe edits | Application metadata and ownership-aware edits |
| Weighted layout grid | Weighted cells with a linear fallback (3.2.0+) |
Operational guides
These longer guides cover application behavior around the payloads. Their coverage is stated explicitly.
| Guide | Coverage |
|---|---|
| Multi-select compatibility | Ten native consumers; 15 payloads per language |
| Workflow state and effects | Tested Python reference application; portable acceptance criteria |
| Bounded delivery | Tested Python SQLite/HTTP application; no exactly-once claim |
| Live prerequisites | Offline readiness inventory; no automatic live-pass claim |
See Sending messages for SDK/HTTP handoff and API reference for signatures. Live tests additionally require an authorized app, genuine resources and interaction receipts.