I've just started encountering the same error message when uploading a file to a folder in Google Drive. I'm aware that we need to reauthorize the connection every 7 days, and it has always worked previously. However, it's not functioning at the moment. This is quite unusual.

Refer to section 3b below. Ensure all scopes are selected.

Follow this guide on setting up a custom OAuth 2.0 app in callin.io.

Additional supplementary instructions are provided below if the above is unclear.

Enable APIs

1. Enable the relevant APIs you wish to use

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

• Navigate to each API page you intend to use and click “Enable”

• Typically, you'll want to enable at least Drive (which 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 Google Redirect URIs for your app

Google Redirect URIs

Here are some commonly required redirect URIs for your Google Cloud Console OAuth app. Setting these up allows you to reuse the same GCP app for other Google apps and modules on callin.io.

 https://www.callin.io/oauth/cb/google 
https://www.callin.io/oauth/cb/google-custom
 https://www.callin.io/oauth/cb/google-restricted 
https://www.callin.io/oauth/cb/google-cloud-speech
 https://www.callin.io/oauth/cb/youtube 
https://www.callin.io/oauth/cb/oauth2
 https://www.callin.io/oauth/cb/oauth2 

Note: After setting these up, you can use/reuse the same callin.io connection for all supported Google apps & modules on callin.io – you will only need 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 Authorized Domains

• Enter callin.io and callin.io

• Complete the other required fields

• Click “Save and Continue”.

  

3b. Add All Scopes

• Click “Add or Remove Scopes”

• Set “Rows per page” to 100. For each page, check all the rows, OR

• Manually input the scopes you require

• Click “Update” at the bottom

  

  1476×1156 182 KB

3c. Proceed to Dashboard

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

3d. Publish your GCP OAuth2 App

Your OAuth application must be set to “Production”; otherwise, the credentials will expire frequently.

• To do this, return to the “OAuth consent screen”

• Then, click the “PUBLISH APP” button

• Next, 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, located on the right side of where you entered the callback URLs in step 2:

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

Enter the callin.io app client ID and secret here BEFORE clicking “Sign in”

(Gmail example)

525×643 65.1 KB

_OR,

4b. HTTP OAuth 2.0 Request Module

708×401 44.2 KB

You need a “Authorize Parameters” key named redirect_uri with the aforementioned callin.io OAuth2 callback URL.

597×904 61.2 KB

Hope this helps! Please let me know if you have any further questions or encounter any issues.

P.S.: Investing some time in the callin.io Academy can save you considerable time and reduce frustration when using callin.io.

Hello,

I wanted to let you know that the previous error I encountered has been resolved. However, during my current testing, I've noticed that the information seems to halt at the tools module. It appears the workflow isn't proceeding past this point.

Could you please help me figure out why the data isn't being passed to the subsequent module and how to fix this issue?

Thank you in advance for your assistance.

Best regards,

gdfg970×544 33.5 KB

qsdq11046×1183 77.4 KB

fssfd1162×1204 96.9 KB

jklkjk955×1741 122 KB

Hello.

I am also encountering the same issue with Google Calendar and have attempted all suggestions from this thread and others, but none have resolved the problem. I'm unsure about the root cause.

Screenshot 2024-11-06 at 12.16.01 PM2714×1324 297 KB

I have followed this guide 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

Screenshot 2024-11-06 at 12.14.04 PM3316×1630 336 KB

• Enable APIs for Google Calendar

(refer to the screenshot above)

• Configure your OAuth consent screen for Google Calendar

Screenshot 2024-11-06 at 12.17.16 PM1714×2638 438 KB

Screenshot 2024-11-06 at 12.16.49 PM1628×674 52.5 KB

• Create your Google Calendar client credentials

I am utilizing the redirect URI ( https://www.integromat.com/oauth/cb/google/ ) as directed in the referenced callin.io guide. I've tried alternative URIs, but they result in an immediate error upon attempting to establish a connection with Google (a 400 URI mismatch error). Using this specific URI permits the connection, but after establishing it, I receive a 403 Insufficient Authentication Scopes error when the module is executed.

Finally, I have deleted and re-established the connection multiple times to ensure a complete refresh, without success. Each instance involved copying and pasting the Client ID and Client Secret directly from the Console.

Not sure how to mark this as resolved, but I managed to get it working. Strangely, I added a different endpoint (which simply returns a list of calendars), and this module prompted me to revalidate (something I had done previously). However, after this revalidation, both the new and the old modules are now running without any issues. Hopefully, this information is helpful to someone in the future!

Hi, could you show some screenshots of how you resolved it?

Hey , unfortunately I didn't capture any at the time, and since the module is connected and functioning, I wouldn't be prompted to revalidate now. Again, I'm not entirely sure why connecting a different module actually helped, but that's the only change I made after posting the notes above.