If you're seeing a "Could not validate access token" error while connecting a Google service to Glide, this article will help you identify the most common causes and resolve the issue.
What This Error Means
When you connect a Google service such as Gmail, Google Calendar, or Google Cloud to Glide, Google issues an access token that allows Glide to securely access the requested service on your behalf.
The "Could not validate access token" error indicates that Google either:
Rejected the token
Could not verify the token
Did not grant the required permissions
Prevented Glide from accessing the requested service
In most cases, the issue originates from the Google account, browser, or Google Workspace configuration rather than Glide itself.
Before You Begin
Determine whether the issue affects:
All Google accounts
Only one Google account
Only Google Workspace accounts
A specific Google service
This information can significantly narrow down the root cause.
For example:
Scenario | Likely Cause |
All Google accounts fail | Browser or connection issue |
Personal Gmail works, Workspace account fails | Workspace policy or account restriction |
One Workspace account fails, others work | User-specific Workspace configuration |
Gmail and Calendar fail, but Google Maps works | Missing OAuth permissions or Workspace restrictions |
Solution 1: Disconnect and Reconnect the Google Account
The most common cause is an expired or invalid OAuth authorization.
Open your Google Account settings.
Navigate to Security.
Open Third-party apps and services.
Locate Glide.
Remove Glide's access.
Return to Glide and reconnect the Google service.
During reconnection:
Complete the consent flow fully.
Accept all requested permissions.
Ensure popups are allowed.
Disable browser extensions that may interfere with authentication.
Once the connection is re-established, Glide will receive a new access token.
Solution 2: Use an Incognito Window
Browser sessions can occasionally interfere with OAuth authentication.
Open an Incognito or Private Browsing window.
Sign in only to the Google account you intend to connect.
Access Glide.
Attempt the connection again.
This prevents conflicts caused by multiple signed-in Google accounts.
Solution 3: Check for Multiple Google Accounts
If you're signed into several Google accounts simultaneously, Google may authorize a different account than expected.
Recommended Practice
Before reconnecting:
Sign out of all Google accounts.
Sign into only the intended account.
Retry the connection.
This is especially important for Google Workspace users who also have personal Gmail accounts.
Solution 4: Verify Google Workspace Permissions
If you're using a Google Workspace account, your Workspace administrator may have applied restrictions that prevent Glide from accessing certain Google services.
Examples include:
OAuth application restrictions
App access controls
Organizational Unit (OU) policies
Security policy changes
Restricted API access
Even if the connection worked previously, Workspace policies can change without modifications in Glide.
Ask Your Workspace Administrator to Check
API Controls
App Access Control
OAuth App Restrictions
Organizational Unit assignments
Security policies affecting third-party applications
Solution 5: Test With Another Google Account
This is one of the fastest ways to identify whether the issue is account-specific.
Test 1
Connect using a personal Gmail account.
Test 2
Connect using another user from the same Google Workspace domain.
Results Interpretation
Result | Likely Cause |
Personal Gmail works | Workspace-related issue |
Another Workspace user works | Account-specific Workspace issue |
All accounts fail | Browser or environment issue |
Only one account fails | User-specific permissions or security restrictions |
Solution 6: Check Google Account Security Settings
Google may temporarily restrict OAuth access if it detects unusual account activity.
This can happen after:
Password changes
Multi-factor authentication changes
Security reviews
Suspicious login detection
Account recovery events
Steps
Open your Google Account.
Navigate to Security.
Review recent security events.
Complete any pending verification requests.
Retry the connection.
Solution 7: Verify Service Availability
Some Workspace users may not have access to the service Glide is attempting to connect.
For example:
Gmail disabled for the user
Google Calendar disabled
Google Cloud access removed
If the underlying Google service is unavailable for that user, Google may reject the authorization request.
Check with your Workspace administrator to confirm the service is enabled for the affected account.
Solution 8: Disable Browser Extensions Temporarily
Privacy-focused browser extensions can interfere with OAuth authentication.
Examples include:
Ad blockers
Tracking protection tools
Privacy extensions
Script blockers
Temporarily disable these extensions and retry the connection.
Common Scenarios
Personal Gmail Works, Workspace Account Fails
Most likely causes:
Workspace security restrictions
OAuth app approval requirements
Organizational Unit policies
Missing service permissions
One Workspace User Fails, Others Work
Most likely causes:
User-specific restrictions
Organizational Unit differences
Security flags on the account
Missing service licenses
Gmail and Calendar Fail, But Other Google Services Work
Most likely causes:
Missing OAuth permissions
Workspace restrictions affecting specific Google services
Incomplete authorization grant
When to Contact Your Workspace Administrator
Contact your Google Workspace administrator if:
Only Workspace accounts are affected.
The issue affects only specific users.
The connection previously worked and stopped unexpectedly.
OAuth-based Google services fail while other Google services continue to work.
Your administrator can verify whether security policies, app access controls, or account permissions are preventing the connection.
Still Having Trouble?
If you've completed all troubleshooting steps and the issue persists, gather the following information before contacting support:
The Google service you're connecting
Whether you're using a personal Gmail or Google Workspace account
Whether other Google accounts can connect successfully
The exact error message shown
Screenshots of the error, if available
Providing this information can help narrow down whether the issue originates from the Google account, Workspace configuration, browser environment, or authorization process.