Frequent Google connection issues

[RH_CEP]

What is your goal?

My goal is to maintain a stable and continuous connection between Make and my Google account (Gmail, Drive).

What is the problem?

I connected Make to my Google account (Gmail, Drive) before the rollout of the new faster connection feature. Since then, my Google connection in Make regularly disconnects without any clear reason.

Do you know what could be causing this issue and how I can fix it?

I would like to avoid reconnecting again, as this would require updating a large number of modules in my scenarios.

What have you tried so far?

Each time the issue occurs, I click Reauthorize and Verify in Connections section .
It temporarily resolves the problem, but only for a short period — usually a few weeks — before the connection drops again.

[Karmic]

I had the same issue and fixed it by switching to a more stable Google OAuth 2.0 Setup.

Here’s a short video on exactly how to do it step by step in Make.com (using your own Google Cloud OAuth so the token stops randomly dying):

Google OAuth 2.0 Setup

Follow the video and wire that new connection into your scenarios and you should stop seeing the recurring “Reauthorize” errors.

I hope this helps you!

[samliew]

Welcome to the Make community!

How to Connect and Use Google APIs in Make!

0. Prerequisites

• 0.1. You need to have a Google account

  Make sure you can sign in to Google Cloud Console with this.

• 0.2. Create a Google Cloud Platform (GCP) project

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

1. Enable Google APIs

• 1.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.

  

---

2. 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

  

  Insert All 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/oauth2
  https://www.make.com/oauth/cb/google
  https://www.make.com/oauth/cb/google/
  https://www.make.com/oauth/cb/google-email
  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/google-search-console
  https://www.make.com/oauth/cb/google-analytics-4
  https://www.make.com/oauth/cb/google-ads2
  https://www.make.com/oauth/cb/google-ads2/
  https://www.make.com/oauth/cb/youtube
  https://www.make.com/oauth/cb/chrome
  

  Including These Google Redirect URIs

  You are also required to insert the legacy URLs below from the old Integromat system that not been migrated to Make yet (same as the above list, but replace “make” with “integromat”):

  https://www.integromat.com/oauth/cb/oauth2
  https://www.integromat.com/oauth/cb/google
  https://www.integromat.com/oauth/cb/google/
  https://www.integromat.com/oauth/cb/google-email
  https://www.integromat.com/oauth/cb/google-custom
  https://www.integromat.com/oauth/cb/google-restricted
  https://www.integromat.com/oauth/cb/google-cloud-speech
  https://www.integromat.com/oauth/cb/google-search-console
  https://www.integromat.com/oauth/cb/google-analytics-4
  https://www.integromat.com/oauth/cb/google-ads2
  https://www.integromat.com/oauth/cb/google-ads2/
  https://www.integromat.com/oauth/cb/youtube
  https://www.integromat.com/oauth/cb/chrome
  

  Note 1: Due to inconsistencies in Make’s implementation of the connections, there are two separate entries where has one is google and another ending in a forward slash google/ - you might need one or the other, so we have to use both!

  Note 2: Once you’ve set these up, you can use/reuse the same Google OAuth App ID + Secret for all the supported Google connections and modules on Make - you’ll just have to enable the relevant Google APIs!

---

3. 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

  

---

4. 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.

  

---

Related Topics:

• Gmail/Google Drive verification issues (error 400): how to solve

Hope this helps! If you are still having trouble, please provide more details.

— @samliew
_{P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!}

[RH_CEP]

Thanks a lot, but that’s exactly what I did.
The issue is that the connection fails about once a month even though I don’t change anything. I just need to reauthorize it and then everything works again. It’s really annoying.

[samliew]

Great, however since I can’t see what exactly you did (or didn’t), you’ll need to redo the connection and show screenshots of each step so that I can walk through it.

Urgent / Private Support

You can use the Hire a Pro category to post a request for private 1-to-1 assistance via video call/screenshare/private messaging/etc. This may help you get your issue resolved faster especially if it is urgent or contain sensitive information. It is important to post your request in the Hire a Pro category, as forum members are not allowed to advertise their services in other categories like here (even if it’s free/unpaid). Posting in the Hire a Pro category will allow other members to assist you over other forms of communication.

How to Message Another User

You can use the private messaging feature to directly reach out to other forum members. To do this, go to your inbox, and click on the “New Message” button on the right.

Alternatively, you can also click on clicking on their username/avatar, then click on the “Message” button in the popup card.

Note: New forum users do not have permissions to send private messages. You can earn trust levels by being active on this forum.

— @samliew