Reauthorizing paid Google Workspace connection

How To
1

Hi,

My Google connection has to be reauthorized every week or so in Make and it’s quite annoying to have to remember to do it.

I’ve read some other posts in the community, and they say that this should only happen for free Gmail accounts, not paid Google Workspace accounts.

However, I do have a paid Google Workspace account, and this is still happening. It causes my automations to break randomly, and I have to go in and reauthorize, and then run all of the unprocessed executions.

Any thoughts on how I can deal with this?

2

Heya @advmt :wave:

This post post could be helpful:

1 Like
3

Thanks. I just replied to that thread, but will also say here:

I do have a paid Google Workspace account (Google Workspace Starter), so that should fulfill Option 1 right?

So why is this still happening ?

4

Did you figure this out? I’m new to make.com but currently struggling with this issue. For me, it keep requiring reauthorization every few hours and even after I reauthorize, the reauthorize button is still there. I tried with free and paid google accounts and the same thing.

5

no never resolved it

6

Welcome to the Make community!

For personal Google accounts, you need to create a private GCP app and link to it instead of using the default connection that Make provides.

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

1476×1156 182 KB

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.

488×581 35.4 KB

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

575×505 33.6 KB

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

1002×683 45.6 KB

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.

597×904 61.2 KB

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:

708×401 44.2 KB

B. Google App

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

525×643 65.1 KB

samliew – request private consultation

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

2 Likes
7

wow thank you so much for that comprehensive answer! I really appreciate it so much. I’ll try it out and hopefully that resolves the issue. I thought I could use a paid google account to avoid the problem but since you never have to reauthorize, it’s worth trying this instead. That’s why I initially tried my personal account because I assumed that there were some limitations with paid.

8

Oh, no, a “paid” Google account (Google One), doesn’t give you any special benefits. Google One is mainly a purchase for personal additional storage, and has no effect on what you do with the Google Cloud Platform which is built to be an enterprise product which has a different billing system.