Google Cloude Storage, Requests to verify connection every day

[Jens]

What is your goal?

I’m using the Google Cloud Storage module to upload a CSV file that gets refreshed daily and then queried through BigQuery. The upload itself works, but the connection breaks every single day.

The automation fails with the following message:

AccountValidationError
Failed to verify connection ‘Google Cloud Storage – Project: Internal’. Status Code: 400

When I open the connection settings and re-authorize the account, everything works again. After some hours or the next day the same error returns and the connection needs to be re-authorized once more.

I haven’t found any related issues or an explanation for why the connection keeps expiring. Any guidance would be appreciated.

[Jens]

no one any idea how to fix this?

[Jacob_Roper]

Hi @Jens,

Is your project in testing mode? If so I would try changing this to production and seeing if the issue still occurs.

I’m not too familiar with this but did a bit of digging and this seems like a potential cause.

Just a quick edit here as well - this thread from Michaela may be able to help: Gmail/Google Drive verification issues (error 400): how to solve

Best regards,
Jacob

[samliew]

@Jens

After some hours or the next day the same error returns and the connection needs to be re-authorized once more.

See Step 3(d).

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

[stephenrodgers1990]

Daily re-verification sounds like an OAuth token scope or refresh issue rather than a real connection problem. I work more smoothly with long-lived service accounts because they avoid prompts and keep automations stable. Setting up a dedicated key, checking expiration windows, and confirming that Make is using the correct authentication flow usually prevents these interruptions and keeps the workflow running reliably.

[Valiant_Racer]

I think the issue here might be related to the refresh token. it’s possible to exempt apps from reauthorization by making them “Trusted”. I would request you to mark the Make app as trusted from your Google Admin, as shown below

Also update the Control session for the specific GCP to mark it as trusted and you can define re-auth period to Never require reauthentication (Option1) in the below image

[Jens]

Hey! Thanks all for your help.

We did everything, but still the same error.

The App ist published, and we changed Make to trusted in the Google Admin…

[Karmic]

@Jens Have you tried checking Make.com for the advanced settings of this connection?

Please confirm if the Client ID / Client secret are the ones from the published GCP project.

If it is, then you should file a ticket here, Make Support (you have to login first), with the following details:

• Connection Name & App
• GCP Project ID & oAuth client ID
• Describe the exact error
• Add a link to the failed run in the scenario history

I hope this helps you!