Google Drive
Personal connection
Each team member connects their own Google Drive account. On Belay stores a personal credential per user, so Claude accesses data scoped to that individual's permissions.
How to connect
Prerequisites: Make sure the Google Drive API is enabled in your Google Cloud Console project and your account has the necessary access.
Google Drive uses OAuth. Connect via the OAuth flow (coming soon).
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 Google Drive. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
https://www.googleapis.com/auth/drive.readonly | Read files | Read only |
https://www.googleapis.com/auth/drive.file | Read/write files created by this app | Read / Write |
https://www.googleapis.com/auth/drive.metadata.readonly | Read file metadata | 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/google 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 →