Salesforce
Org-level connection
Salesforce 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 authorize On Belay to access your Salesforce org. You'll be redirected to Salesforce to approve the connection — no credentials to copy or paste.
Note: A Salesforce admin must first create a Connected App (Setup → Apps → App Manager → New Connected App) with OAuth enabled and On Belay's redirect URI added. The admin must also approve the app before users can connect.
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 Salesforce. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
api | Full API access | Read / Write |
leads:read | Read leads | Read only |
contacts:read | Read contacts | Read only |
opportunities:read | Read opportunities | Read only |
accounts:read | Read accounts | Read only |
reports:read | Read reports | 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/salesforce 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 →