Same here setting up the connection with Google Drive module:
Update:
I believe I have found an issue with the Google Drive connector when creating a new OAuth connection.
Environment
- Make region: US2
- Google Drive module: Create a Folder
- OAuth Client: Custom OAuth (Web Application)
- Google Cloud project is in Testing mode.
- My Google account is added as a Test User.
OAuth configuration
The OAuth flow completes successfully.
Google redirects back to Make using:
https://us2.make.com/oauth/cb/google-drive
The callback URL contains a valid authorization code, for example:
code=4/0AXEQ...
This indicates that:
- Authentication succeeds.
- Consent is granted.
- Google generates a valid Authorization Code.
- Redirect URI is correctly configured.
Therefore, the OAuth authorization phase completes successfully.
Problem
Immediately after the redirect back to Make, the connection creation fails with:
{
"message": "The request failed due to failure of a previous request.",
"code": "SC424",
"suberrors": [
{
"message": "Cannot assign to read only property 'scope' of object '#<Connection>'",
"name": "TypeError"
}
]
}
The browser developer tools show the following internal debug information:
{
"message": "The request failed due to failure of a previous request.",
"code": "SC424",
"suberrors": [
{
"message": "[401] Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential.",
"name": "RuntimeError"
}
],
"debug": [
[
"google-drive:",
"request",
"GET",
"https://www.googleapis.com/oauth2/v2/userinfo",
{
"headers": {
"authorization": "***"
}
}
],
[
"google-drive:",
"response",
401,
{
"body": {
"error": {
"code": 401,
"status": "UNAUTHENTICATED"
}
}
}
]
]
}
Why I believe this is a Make issue
I have verified the following:
- OAuth Client is configured as Web Application.
- Redirect URIs are correctly registered, including:
https://www.make.com/oauth/cb/google-drive
- Test User is configured.
- OAuth Consent Screen is configured correctly.
- The issue occurs in a completely new scenario.
- The issue occurs with different Google Drive modules.
- Google successfully returns an Authorization Code before the failure.
Since Google already issued the authorization code and redirected back to Make successfully, the failure appears to occur during Make’s token exchange or while storing/retrieving the access token before calling the Google UserInfo endpoint.
It seems that the Google Drive connector is attempting to call:
GET https://www.googleapis.com/oauth2/v2/userinfo
without a valid OAuth access token, which results in:
401 UNAUTHENTICATED
The subsequent SC424 and Cannot assign to read only property 'scope' errors appear to be secondary errors triggered by the failed authentication.
Could you please investigate whether this is a regression or an issue affecting the Google Drive connector on the US2 cluster?
If needed, I can provide my Scenario ID, Organization ID, Google Cloud configuration, and HAR files for further investigation.
Thank you very much for your assistance.
What is your goal?
What is the problem & what have you tried?
Error messages or input/output bundles
Screenshots (scenario flow, module settings, errors)
