The LithoBlocks blog
Product guides / Engineering / IdeasIdeas you can build on.
Explore the engine, design useful interactions,
Featured guide / Start here
Most automated Slack messages are ignored. Here's how to structure, format, and write messages that people actually act on.
Read the guide ↗8 articles
A Slack message that updates when action is taken isn't just a nice UX detail: it prevents duplicate work, creates an automatic audit trail, and closes the loop on every alert you send.
DeliveryDMs and channels solve different problems. The wrong choice creates noise for everyone, or hides information that should be shared. Here's the framework for getting it right.
DeliveryBlock Kit has hard limits on blocks, characters, and elements that will silently truncate or reject your messages. Here's what they are and how to design around them.
DesignModals and messages both support interactivity in Slack, but they serve different purposes. Here's how to decide which one your workflow actually needs.
DesignMost Slack alerts are either too noisy or too vague. Here's a concrete template for alerts that get the right response without training people to ignore them.
DesignBuild useful Slack tables with the current native schema, column alignment, wrapping, and data-driven LithoBlocks templates.
DesignConnect Slack buttons to Make with LithoBlocks webhook destinations, inspect delivery, and update the original message after an action.
IntegrationsWhen every event gets its own Slack message, people stop reading all of them. Here's how to design notification systems that stay useful as they scale.
DeliverySlack + LithoBlocks
The visual workspace and engine for your next Slack experience.
LithoBlocks