Prompt
Slack App Directory integration setup for a B2B app
Latest observation
If you’re setting up a Slack App Directory integration for a B2B app, the main goal is usually:
- Let a workspace admin install your app
- Request only the right Slack scopes
- Handle OAuth securely
- Make the app useful for teams across an organization
- Pass Slack review if you plan to list publicly
Here’s a practical setup guide.
1) Decide the integration model
For a B2B SaaS app, Slack integrations usually fall into one of these patterns:
- Single-workspace install: one customer workspace connects to one SaaS tenant
- Multi-workspace / org-wide: one company may connect several workspaces
- Enterprise Grid support: for larger customers, often required if you target enterprise accounts
- Public App Directory listing: discoverable by any Slack customer
- Private distribution: install by direct link, not listed publicly
If you want broad B2B adoption, design for:
- Self-serve install
- Admin-friendly permissions
- Workspace-to-tenant mapping
- Enterprise Grid readiness
2) Create the Slack app
In the Slack API dashboard:
- Create a new app
- Choose the correct workspace for development
- Set:
- App name
- Short description
- Long description
- Icons
- App home
- Support / privacy policy URLs
- Terms of service
- Redirect URLs
If you plan to list in the App Directory, these fields matter for review and trust.
3) Configure OAuth and redirects
Enable OAuth & Permissions.
Add your redirect URL, for example:
https://yourapp.com/slack/oauth/callback
Your app should handle the standard flow:
- User clicks “Add to Slack”
- Slack redirects to your authorization URL
- User approves scopes
- Slack redirects back with
code - Your backend exchanges
codefor:access_tokenorbot_tokenteam_identerprise_idif present- granted scopes
Store the installation securely and associate it with your customer org.
4) Choose scopes carefully
Slack reviewers and admins care a lot about scopes.
Best practices
- Request the minimum scopes required
- Prefer bot token scopes over legacy broad access
- Avoid requesting sensitive scopes unless essential
- Explain clearly why each scope is needed
Common B2B app scopes
Depending on features, you might need:
chat:write— send messageschannels:read— see public channelsgroups:read— see private channels if necessaryim:write— open DMsusers:read— user lookupcommands— slash commandsapp_mentions:read— respond when mentionedincoming-webhook— post via webhook URL
Only request private-channel access if your product truly needs it.
5) Build the installation data model
For B2B SaaS, you’ll usually need a table for Slack installations keyed by:
enterprise_idteam_idbot_user_idaccess_token- granted scopes
- installation status
- connected SaaS tenant/account ID
Important design choice:
- If your SaaS has one account per company, link Slack workspace(s) to that company account.
- If your SaaS supports multiple business units, allow multiple Slack installs per tenant if needed.
6) Add account linking
In a B2B context, Slack install alone is often not enough.
Common pattern:
- Admin installs Slack app
- Then they’re asked to connect the Slack workspace to their SaaS org
- You verify they’re authorized in your app
- You map the Slack team/workspace to the customer account
Useful for:
- Billing
- permissions
- workspace-specific settings
- audit logs
7) Handle event subscriptions or interactive features
Depending on the app, configure one or more of:
- Event Subscriptions
- message events
- app mentions
- member joined
- channel events
- Slash commands
- Interactivity & Shortcuts
- buttons
- modals
- message actions
- App Home
- dashboard-like UX inside Slack
For B2B apps, App Home is often useful as a central place to show:
- connected status
- recent activity
- configuration
- support links
8) Support enterprise and compliance requirements
B2B buyers often expect:
- SSO support
- SCIM / user provisioning alignment
- Audit logging
- Data retention controls
- Admin controls
- Security documentation
- SOC 2 / ISO alignment if applicable
Slack-specific trust items:
- clear data handling explanation
- no unnecessary message storage
- visible privacy policy
- ability to uninstall and revoke access cleanly
9) Prepare for Slack App Directory review
If you want public listing, Slack will review your app.
Review usually looks at:
- functionality
- scope justification
- branding
- error handling
- auth flow
- user experience
- privacy policy
- data usage
- support responsiveness
Common review pitfalls
- Requesting too many scopes
- Unclear purpose
- Broken install flow
- Poor handling of uninstall
- No user-facing value after install
- Hidden or vague data collection
10) Design a solid B2B UX
A good B2B Slack integration usually includes:
- “Add to Slack” CTA in your product
- Workspace connection status page
- Admin-only configuration
- Clear explanations of permissions
- Useful immediate value after installation
- Easy disconnect/reconnect flows
- Notifications for failed sync or revoked permissions
11) Operational concerns
Plan for:
- token rotation / token revocation
- Slack API rate limits
- workspace rename / enterprise grid changes
- app uninstall handling
- multiple installations per customer
- webhook/event retries
- idempotent event processing
12) Recommended implementation checklist
Slack app config
- App created
- OAuth redirect URL configured
- Scopes minimized
- Event subscriptions configured
- Interactivity enabled if needed
- App Home configured
- Support/privacy/terms URLs added
Backend
- OAuth callback implemented
- Installation storage model created
- Token encryption at rest
- Install/uninstall handlers
- Event verification using signing secret
- Retry/idempotency handling
B2B-specific
- Workspace-to-tenant mapping
- Admin authorization checks
- Customer support workflows
- Billing/account linkage
- Audit log visibility
13) If you want public App Directory listing
Make sure you have:
- a polished landing page
- a clear product description
- screenshots or demo materials if requested
- privacy policy
- terms of service
- support contact
- a transparent data policy
- a working install/use flow
If you want, I can also provide one of these next:
- A Slack App Directory launch checklist for B2B SaaS
- A recommended OAuth + token storage architecture
- A scope selection guide based on your app’s features
- A sample Slack App review submission description