LithoBlocks01
Builder
For your first Slack experiences.
$20/mo
500 creditseach month$0.15 per overage credit
- 3 active digest queues
- 500 events / 24 hours
- Fixed-interval digests
- Scheduled & recurring delivery
Pricing & usage
Build more with Slack.
Know what you’ll use.
One shared allowance for your organization. Build your Slack workflows, then pay for the operations you use.
02For growing teams
Team
For teams building across workflows.
$50/mo
1,000 creditseach month$0.10 per overage credit
- 10 active digest queues
- 5,000 events / 24 hours
- All three digest modes
- Scheduled & recurring delivery
03
Business
For operations at a larger scale.
$250/mo
10,000 creditseach month$0.05 per overage credit
- 50 active digest queues
- 50,000 events / 24 hours
- All three digest modes
- Scheduled & recurring delivery
04 / ENTERPRISE
Talk to sales ↗Something more specific?
Let’s talk about your volume, collaboration and support needs.
Prices in USD. Annual subscriptions still receive monthly credit allowances. Overage availability depends on your organization’s settings.
Understand credit usage
Every operation has a clear costA credit is
a unit of work.
One request can reach many people. One digest can collect many events. The operation determines the charge.
01
Direct send
1 creditPer successful Slack delivery. Rendering is included.
02
Standalone compile
1 creditRender a template without posting to Slack.
03
Scheduled delivery
2 creditsPer standalone scheduled occurrence, including recurring sends.
04
Bulk send
1 / destinationOne credit for each successful destination, not for the whole request.
05
Batch digest
Configured costPer delivered digest, not per incoming event. Check your queue’s credit cost.
06
Updates & interactions
No extra creditUpdates, modal interactions and callbacks. Separately triggered sends or compiles are metered.
Collect first. Pay on delivery. Creating a schedule and pushing events into a digest do not spend delivery credits. Event intake limits still apply. Each recurring delivery is charged separately.
Check your digest’s cost. Digests use the credit cost configured on their queue. Bulk sends deliver a separate message to each destination. See worked examples →
Estimate your usage
What does your
workflow use?
Model a month of deliveries and compiles. Count scheduled occurrences and successful bulk destinations individually.
Your monthly estimate
920
credits used
- Included each month
- 1,000
- Credits above allowance
- 0
- Estimated overage
- $0
- Monthly total
- $50/month
Assumes successful operations, enabled overages, no rollover balance, and no custom pricing. Taxes excluded. Event intake and plan restrictions apply separately. This is an estimate, not an invoice.
Digest delivery options
Three ways to
bring events together.
Fixed interval
Collect events in a window that starts with the first event. Deliver the digest when that window closes.
Rolling window
Wait for a quiet spell. Each incoming event extends the collection window.
Fixed volume
Deliver when the batch reaches your event threshold, with a maximum wait so smaller batches still go out.
Paid plans include visual templates, forms, versioning and API access. Queue capacity, event limits and delivery modes vary by plan. Explore digest queues ↗
Frequently asked questions
A little more
clarity.
For your current offer, trial eligibility and subscription terms, see Billing in the app.
Ask a billing question ↗Is one credit always one message?
No. A direct send uses 1 credit and includes rendering. A standalone compile also uses 1 credit without posting a message. A standalone scheduled delivery uses 2 credits. A bulk send uses 1 credit per successful destination, and a digest uses its queue’s configured credit cost.
When do schedules and digests use credits?
Creating a schedule or pushing events into a queue does not spend delivery credits. Credits are deducted during delivery processing. Each recurring delivery is metered separately. Older schedules attached to a queue policy use that policy’s configured cost.
What happens when my credits run out?
If your organization enables overages, processing can continue at your plan’s per-credit rate, subject to any configured overage limit. Otherwise, operations needing more credits stop until credits are available.
Are updates, clicks and modal submissions free?
The interactions themselves use no additional message credit. If an action triggers another send or a standalone compile, that separate operation uses credits at its normal rate. Authoring validation is also free; a rendered compile is not.
What if a delivery fails or a request times out?
Known failed queue deliveries can refund reserved credits. A timeout alone does not establish whether a message was delivered or charged. Check usage and delivery logs before retrying; reuse the same idempotency key for the same supported operation.
How does annual billing work?
The listed annual plans save 15% against twelve monthly payments. Credit allowances remain monthly. Check your organization’s Billing page for your next renewal, available balance and subscription terms.