Google Restricted Connection keeps getting cut

Hi everyone,

First post here, sorry if the formatting isn’t adequate.

I’m having an issue in my scenario where my Google Restricted Connection keeps getting “unauthorized” and I have to come back manually every 3-4 days to allow the connection again.
Otherwise my scenarion doesn’t run automatically every hour.

The normal Google Connection has no issue and stays linked but the Restricted one somehow gets reset every few days.

Any insights as to why that is and how I could fix this issue ?

Thank you very much for your time.

This is Google’s way of telling you “don’t use restricted connections”. Not sure there is a clear way of using Restricted Connections with nonexpiring connections.

1 Like

Welcome to the Make community!

I have set up my connection properly and it has never expired yet after a year.

How to create an OAuth app in GCP: https://www.make.com/en/help/tutorials/calling-google-apis-via-the--http-make-a-oauth-2-0-request--module ← FOLLOW THIS

1a. Enable the relevant API

Find the relevant API here: Google Cloud console
Go to API page, end click “Enable”

1b. Add the relevant scopes

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

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

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

Here are some known 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.

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.

3. Publish your GCP OAuth2 app

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

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

1. To do this, go to menu item “OAuth consent screen”

or click here https://console.cloud.google.com/apis/credentials/consent

2. Then click the button below if the Publishing status is not “In production”

4. Set up connection (HTTP OAuth, or respective Google App)

A. HTTP OAuth2

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

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 8 callback URLs in step 2:

B. Google App

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

samliewrequest private consultation

Join the unofficial Make Discord server to chat with other makers!

1 Like

Yes I think step 3 is important to publish the app in gcp and set it to in production.

1 Like