Google connectors
Fix a Google connector whose setup fails or whose grant Google refuses.
A Google connector reaches Google through your own Google Cloud project. Create a Google Cloud project sets it up. A connector shows a problem as a condition among its current problems.
A condition names a scope, such as google:scope:...
The grant lacks a permission the connector needs, because it was cleared on Google's consent screen. The connector does nothing that needs it.
Run --setup <file> again, leave every permission ticked, and put the new token in every Google connector.
Setup reports access_denied
You declined on the consent screen, or Google or an administrator blocked the request. An account in Google's Advanced Protection Program lets only Google apps and verified apps reach its data, so it can block an app Google hasn't verified. Setup's log says which cause to check.
Approve the request, or sign in with an account that isn't in the program.
Setup reports admin_policy_enforced
A Google Workspace administrator restricts the client or a scope.
Ask the administrator, or use a personal Google account.
A condition says the client is wrong (google:client)
Google refused the client.
Check that GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET belong to the Desktop app client, and restart the connector.
A condition says the account is different (google:account)
The grant belongs to another Google account than the one the connector keeps, which is the account it first ran with, or the one its items came from.
Run --setup <file> again and sign in with the original account, or use another instance.
Google reports deleted_client
Google deletes an OAuth client that goes unused for six months, and its tokens stop working.
Create a new Desktop app client, put its ID and secret in every Google connector's environment, then reconnect.
Covered in their guides
| What you see | Guide |
|---|---|
A condition google:reconnect | Reconnect |
A connector run ends with an exit code other than 0 | Exit codes |