Slack
Org-level connection
Slack is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
How to connect
Click "Connect with OAuth" below to install the On Belay app to your Slack workspace. You'll be taken to Slack to approve the connection — no credentials to copy or paste.
Ready to connect?
Go directly to the integrations page in your dashboard.
Permissions (scopes)
These are the data scopes On Belay can be granted for Slack. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
channels:read | List and read public channels | Read only |
channels:history | Read public channel messages | Read only |
groups:read | List private channels | Read only |
groups:history | Read private channel messages | Read only |
im:read | List direct messages | Read only |
im:write | Open direct message conversations | Read / Write |
im:history | Read direct messages | Read only |
mpim:read | List group direct messages | Read only |
mpim:history | Read group direct messages | Read only |
chat:write | Post messages | Read / Write |
chat:write.public | Post to channels without joining | Read / Write |
users:read | View workspace members | Read only |
users:read.email | View member email addresses | Read only |
files:read | Read files | Read only |
reactions:read | Read emoji reactions | Read only |
team:read | Read workspace info | Read only |
Troubleshooting
"redirect_uri_mismatch" error during OAuth
Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add https://app.onbelay.ai/api/oauth-callback/slack to the allowed redirect URIs in your OAuth app settings.
"invalid_scope" error
The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g., Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
Still stuck? We're happy to help.
Contact support →