You’re thinking about adding an app to the Slack Marketplace. You know what it is and what it offers. Now the question is whether your app belongs there.
Not every good Slack app is a good fit for the Slack Marketplace. That’s ok! Some of the most useful Slack apps never need to leave the building. But it’s important to understand up front what makes a good Slack Marketplace app and what to expect when you start the process.
Whether an app is right for the Marketplace comes down to three things: external demand, multi-workspace support, and readiness to provide ongoing support.
Does anyone outside your company need this?
Start here. If your app solves a problem that’s specific to your org (talking to your internal tools, your databases, your particular workflows) then it’s an internal Slack app. Keep it on your workspace(s) and skip the Slack Marketplace process entirely.
But if your app tackles something more universal (e.g. incident response, standup automation, project updates) there’s a good chance teams at other companies want it too. If someone has already asked you about it, you have external demand.
Can your app support more than one workspace?
Once you’ve confirmed there’s demand beyond your org, the next question is technical. On the Slack Marketplace, anyone can install your app. That means your app needs to support:
Separate credentials per workspace. Every install generates its own access tokens. These are the keys your app uses to interact with that workspace’s data. You need to store and retrieve them per-workspace without mixing things up.
Data isolation. Users in Workspace A should never see data from Workspace B. No exceptions.
A working install flow. When someone clicks “Add to Slack,” your app walks them through an OAuth authorization process that grants access to their workspace. This needs to work for any workspace, not just yours.
You’ll also need at least 5 active workspace installs before you can submit to Slack Marketplace.
Can you support your app like a product?
Listing on the Slack Marketplace means you’re maintaining a product that other teams depend on. For this you’ll need:
A landing page. This is where potential users learn what your app does before they install it. It should explain what the app does, show how it works, and link to your privacy policy and support page. The Slack Marketplace listing links out to it, so it needs to be public and accessible without logging in.
A public support page. Provide a way for any user to reach you. They shouldn’t need to create an account to ask for help. A contact form or email works and a timely response is required.
A privacy policy. Explain what data you collect, how long you keep it, and how users can request deletion. Link it from your app’s landing page so anyone can find it without logging in. A clear, specific policy builds trust with the teams that install your app.
A stable app. Teams expect apps they install from the Slack Marketplace to work consistently. Show users helpful messages when something goes wrong. Make your uninstall process clean and predictable.
Updates as needed. Update your listing when things change. Adopt new security features as they’re released. Resubmit for review when you make significant changes. Staying active and well-maintained builds trust with your users over time.
What’s your next move?
If you checked most of those boxes, you’re in good shape to move forward. Review the official requirements and start the submission process.
If you have some gaps, focus on these in order:
- 1. Build your install flow so other workspaces can authorize your app
- 2. Get at least 5 active workspace installs
- 3. Set up your support page and privacy policy
- 4. Double check the requirements before submitting
We also have this self-assessment to help you decide if your app is right for the Slack Marketplace.
This is the second post in a series on building for the Slack Marketplace. For background on what the Slack Marketplace is and how apps get listed, see From One Workspace to Every Workspace. Next up: Marketplace Best Practices.
