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.
Getting your API key
Go to api.slack.com/apps → Create New App → From scratch
Add OAuth scopes as needed
Install to workspace and copy the Bot User OAuth Token
Paste it below
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 | Read channels | Read only |
channels:history | Read channel history | Read only |
messages:write | Write messages | Read / Write |
users:read | Read users | Read only |
files:read | Read files | Read only |
Troubleshooting
"Invalid API key" or "Unauthorized" error
Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.
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.
The key expires or stops working
Some API keys have expiration policies. Generate a new key in Slack and update it in On Belay → Integrations → Slack → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.
Still stuck? We're happy to help.
Contact support →