Issue with Google Calendar Module: Error 403 "Request had insufficient authentication scopes

Hello,

I am currently facing an issue with the Google Calendar module when using it with Make. When I attempt to access calendar data or perform actions, I encounter the following error:

“403 - Request had insufficient authentication scopes”

This error seems to indicate that the necessary permissions to access certain Google Calendar features are not correctly defined or granted in the OAuth authentication settings. I want to clarify that I have properly created an API and configured the OAuth redirects, as well as the permissions granted, but the issue persists.

I would appreciate your help in identifying and resolving this error. It is possible that I need to add additional scopes or reconfigure the authentication to allow the module to access the requested resources correctly.

Could you please guide me on the steps to take or any necessary changes in the API configuration to fix this issue?

Thank you in advance for your assistance.

I just started receiving the same error message when uploading a file to folder in google drive. I know every 7 days we need to reauthorize the connection and it always worked. At this time, it’s not. This is odd.

See 3b below. Make sure you have selected ALL scopes.

Follow this main guide on how to set up a custom OAuth 2.0 custom app in Make.

Provided below are additional supplementary instructions in case the above isn’t clear enough.


Enable APIs

1. Enable the relevant APIs that you want to use

Search for the relevant Google API here: https://console.cloud.google.com/apis/library

  • Go to each API page that you want to use, end click “Enable”

  • Usually you’ll want to enable at least Drive (includes Docs/Sheets) and Gmail.


OAuth Client

Direct Link: https://console.cloud.google.com/apis/credentials

2a. Create “OAuth client ID” Credentials

2b. Insert all the Google Redirect URIs for your app

Google Redirect URIs

Here are some commonly-needed redirect URIs you need for your Google Cloud Console OAuth app. If you set these up, you can reuse the same GCP app for other Google apps and modules on Make.

https://www.make.com/oauth/cb/google
https://www.make.com/oauth/cb/google-custom
https://www.make.com/oauth/cb/google-restricted
https://www.make.com/oauth/cb/google-cloud-speech
https://www.make.com/oauth/cb/youtube
https://www.make.com/oauth/cb/oauth2
https://www.integromat.com/oauth/cb/oauth2

Note: Once you’ve set these up, you can use/reuse the same Make connection for all the supported Google apps & modules on Make - you’ll only have to enable the APIs for your custom app.


OAuth consent screen

Direct Link: https://console.cloud.google.com/apis/credentials/consent/edit

3a. Insert Two Authorised Domains

  • Insert make.com and integromat.com

  • Fill in other required fields

  • Click “Save and Continue”.

3b. Add All Scopes

  • Click “Add or Remove Scopes”

  • Select 100 “Rows per page”, for each page, check all the rows, OR

  • Manually type in the scopes you need

  • Click “Update” at the bottom

3c. Step through and go to dashboard

At the last step/page, click “BACK TO DASHBOARD” instead of “Prepare for Verification”

3d. Publish your GCP OAuth2 app

You will need to set your OAuth application to “Production”, otherwise the credentials expire very frequently.

  • To do this, go back to “OAuth consent screen

  • Then click the “PUBLISH APP” button

  • Then click the “CONFIRM” button


Create New Connection (HTTP, or respective Google module)

You can find the Client ID and Client Secret in the OAuth2 app you created in GCP, on the right-hand side of where you inserted the callback URLs in step 2:

4a. Specific Google module (Sheets, Docs, Drive, Gmail, etc.)

Insert the GCP app client ID and secret here BEFORE clicking “Sign in”

(Gmail example)

OR,

4b. HTTP OAuth 2.0 Request module

You need a “Authorize Parameters” key of redirect_uri with the above Make OAuth2 callback URL.

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Hello,

I would like to inform you that the previous error I encountered has been resolved. However, during my current tests, I notice that the information stops at the tools module. It seems that the flow does not continue beyond this point.

Could you please assist me in identifying why the information isn’t passing to the next module and how to resolve this issue?

Thank you in advance for your help.

Best regards,




Hello.

I’m also experiencing the same issue for Google Calendar and I’ve tried everything listed in this thread as well as the others and none of the recommendations are helping. Not sure where the issue is hiding.

I’ve followed this document to the best of my ability: https://www.make.com/en/help/app/google-calendar#create-and-configure-a-google-cloud-console-project-for-google-calendar

  • Create a Google Cloud Console project for Google Calendar

  • Enable APIs for Google Calendar

(see screenshot above)

  • Configure your OAuth consent screen for Google Calendar


  • Create your Google Calendar client credentials

I’m using the (https://www.integromat.com/oauth/cb/google/) redirect URI as instructed in the linked Make.com guide above, I’ve experimented with others but get an error immediately upon tryin to establish the connection to Google (400 URI mismatch error). Using this URI allows me to make the connect but once I do I get the 403 Insufficient Authentication Scopes error when I actually execute the module.

Lastly, I’ve deleted and re-established the connection multiple times to ensure it’s completely refreshed to no avail. Each time I’ve copied and pasted the Client ID and Client Secret directly from the Console.

Not sure how to mark this as resolved but I was able to get it working. Oddly, I added a different endpoint (simply return a list of calendars) and this module prompted me to revalidate (which I had previously done). However, after this revalidation, both the new and the old modules now run without issue. Hopefully that helps someone in the future!

Hi @Acton could you show some screen shots of how you resolved it?

Hey @Callee_AI_Solutions, unfortunately I did not grab any at the time and since the module is connected and working I wouldn’t be prompted to revalidate now. Again - I’m not actually sure why connecting a different module actually helped but that’s the only thing different that I tried after posting the notes above.