PPlatformAppStores

Slack App Directory

Workspace

Slack Technologies, LLC · Productivity & collaboration suites

Best for: Workflow, notification, and productivity bots for teams working in Slack.

Overview

Slack App Directory lists apps built on the Slack platform, spanning bots, slash commands, message shortcuts, and Workflow Builder steps. Public apps use OAuth 2.0 via the "Add to Slack" button, returning scoped bot and user tokens per workspace.

How to build & ship

  1. 1Create an app at api.slack.com/apps (from scratch or a manifest)
  2. 2Build with the Bolt framework (JavaScript, Python, or Java) or the Web/Events APIs directly
  3. 3Configure OAuth scopes, event subscriptions, slash commands, and interactivity endpoints
  4. 4Implement UI with Block Kit and handle events/actions via your listeners
  5. 5Complete the App Directory listing and submit for Slack's review

Key APIs & SDKs

Slack Web API
Events API
Bolt SDK (JS/Python/Java)
Block Kit UI framework
OAuth 2.0 scopes
Incoming Webhooks

Integration types

Bot
Workflow action
Connector

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: Webhook
  • Security review: Required
  • Directory submission review covers security, UX, and Slack API policy compliance.
  • Public apps go through a Slack App Directory review covering OAuth scope justification, security, functionality, and listing quality; commonly cited as roughly one to two weeks.
  • Tiered rate limits per method, enforced per workspace and per app.
Auth docs Store policies

Monetization

Free
Paid app
Usage-based
Onboarding
$0
Commission
0% direct; billing handled by developer
Merchant of Record
Developer is MoR

Pros & cons for builders

Pros

  • Very large developer base and mature, well-documented APIs
  • Bolt SDK and Block Kit make building and interactive UIs fast
  • Strong distribution to businesses already living in Slack
  • Granular OAuth scopes give fine-grained permission control

Cons

  • Directory review enforces strict scope-minimization and security requirements
  • No first-party billing; monetization must be handled externally
  • Maintaining event/interactivity endpoints requires always-on hosting