Gmail / Google Workspace

OAuthCommunication & SupportOrg connectionPersonal connection

Org & personal connection

Gmail / Google Workspace can be connected at the org level (shared credential for all groups) or personally by each team member. Admins set up the org connection; individuals connect their own account for personal access.

How to connect

Prerequisites: Make sure the Gmail / Google Workspace API is enabled in your Google Cloud Console project and your account has the necessary access.

Click "Connect with OAuth" below to authorize On Belay to access your Gmail. You'll be redirected to Google to approve the connection — no credentials to copy or paste.

Connect at the **org level** to share a single inbox (e.g. accounting@yourdomain.com) with all fieldsets. Connect at the **personal level** to use your individual Gmail account.

Ready to connect?

Sign in to On Belay and open the Integrations page to add Gmail / Google Workspace.

Sign in →

Permissions (scopes)

These are the data scopes On Belay can be granted for Gmail / Google Workspace. Your org admin controls which scopes are enabled per group.

ScopeDescriptionAccess
https://www.googleapis.com/auth/gmail.readonlyRead emailRead only
https://www.googleapis.com/auth/gmail.sendSend emailRead / Write
https://www.googleapis.com/auth/gmail.labelsManage labelsRead / Write

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 →