# Reauthorizing paid Google Workspace connection **URL:** \ **Category:** Questions\ **Tags:** connections\ **Created:** [April 15, 2024, 3:05pm UTC](https://community.make.com/t/reauthorizing-paid-google-workspace-connection/33868 "2024-04-15T15:05:53Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![advmt](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@advmt](https://community.make.com/u/advmt)\ **Post date:** [April 15, 2024, 3:05pm UTC](https://community.make.com/t/reauthorizing-paid-google-workspace-connection/33868/1 "2024-04-15T15:05:53Z")
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? ---
**Author:** ![Michaela-Inactive](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/michaela-inactive/32/29_2.png) [@Michaela-Inactive](https://community.make.com/u/Michaela-Inactive)\ **Post date:** [April 16, 2024, 5:27am UTC](https://community.make.com/t/reauthorizing-paid-google-workspace-connection/33868/2 "2024-04-16T05:27:04Z")
Heya @advmt 👋 This post post could be helpful: > [@Gmail/Google Drive verification issues (error 400): how to solve](https://community.make.com/t/gmail-google-drive-verification-issues-error-400-how-to-solve/27432): > > Hey Makers waveAre you running into the “Failed to verify connection. Status Code Error: 400” error in your scenarios featuring Gmail or Google Drive modules? We’ve got some tips to help you overcome it. Understanding the issue thinkingDue to Google’s updated security policy, unpublished apps can only have a 7-day authorization period. After the OAuth security token expires, the connection is no longer authorized and any module relying on it will fail. Preventing Google connecti… ---
**Author:** ![advmt](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@advmt](https://community.make.com/u/advmt)\ **Post date:** [April 17, 2024, 4:06am UTC](https://community.make.com/t/reauthorizing-paid-google-workspace-connection/33868/3 "2024-04-17T04:06:16Z")
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 ? ---
**Author:** ![Joanna1](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@Joanna1](https://community.make.com/u/Joanna1)\ **Post date:** [July 11, 2024, 6:32pm UTC](https://community.make.com/t/reauthorizing-paid-google-workspace-connection/33868/4 "2024-07-11T18:32:37Z")
Did you figure this out? I’m new to [make.com](http://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. ---
**Author:** ![advmt](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@advmt](https://community.make.com/u/advmt)\ **Post date:** [July 12, 2024, 1:28am UTC](https://community.make.com/t/reauthorizing-paid-google-workspace-connection/33868/5 "2024-07-12T01:28:16Z")
no never resolved it ---
**Author:** ![samliew](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/samliew/32/13327_2.png) [@samliew](https://community.make.com/u/samliew)\ **Post date:** [July 12, 2024, 1:46am UTC](https://community.make.com/t/reauthorizing-paid-google-workspace-connection/33868/6 "2024-07-12T01:46:06Z")
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](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](https://console.cloud.google.com/apis/library) Go to API page, end click “Enable” ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/d/4/d4727c4eee0426b3415b3cc285eb46d47d9dc6ad.png) # 1b. Add the relevant scopes **Direct Link:** [https://console.cloud.google.com/apis/credentials/consent/edit](https://console.cloud.google.com/apis/credentials/consent/edit) ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/3/e/3ebb5ef4860a9d7319450f72c21ef0d9380e7d25.png) # 2. Insert all the known Google Redirect URIs for your app **Direct Link:** [https://console.cloud.google.com/apis/credentials](https://console.cloud.google.com/apis/credentials) Here are some known redirect URIs you need for your [Google Cloud Console](https://console.cloud.google.com/) OAuth app. If you set these up, you can reuse the same GCP app for other Google apps and modules on Make. ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/0/d/0db2e4be5b8585c864c93fb36ce4533a1798b562.png) 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](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](https://console.cloud.google.com/apis/credentials/consent) ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/a/8/a84332556db5eb5aac7952030e9f6ac129d2c792.png) ### 2. Then click the button below if the Publishing status is not “In production” ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/6/8/68f653cb3050943caef7ce4e18f306b4f5f2ad26.png) # 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. ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/4/3/43df2cd92abedfda53a23fc12991dbfb13eff1be.png) 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: ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/a/e/aeb4ff9ca8e4f5ddf3badd144b4f5a4fb19f27ef.png) ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/8/9/89a1c01d161c36bc11d1e7460256be7e02258d18.png) ## B. Google App Insert the GCP app client ID and secret here **BEFORE** clicking “Sign in” Gmail example: ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/c/a/caa6efb63fb50b12399549ee627da8bb29189a13.png) [samliew](https://samliew.com/services) – [request private consultation](https://samliew.com/request-quote?ServiceType=Automation%20Consultation&Referrer=Make) > Join the [Make Fans](https://samliew.com/make-discord-invite) Discord server to [chat](https://samliew.com/make-discord-invite) with other makers! ---
**Author:** ![Joanna1](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@Joanna1](https://community.make.com/u/Joanna1)\ **Post date:** [July 12, 2024, 10:42pm UTC](https://community.make.com/t/reauthorizing-paid-google-workspace-connection/33868/7 "2024-07-12T22:42:06Z")
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. ---
**Author:** ![samliew](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/samliew/32/13327_2.png) [@samliew](https://community.make.com/u/samliew)\ **Post date:** [July 26, 2024, 1:02pm UTC](https://community.make.com/t/reauthorizing-paid-google-workspace-connection/33868/8 "2024-07-26T13:02:02Z")
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. ---
**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\ **Post date:** [October 24, 2024, 1:09pm UTC](https://community.make.com/t/reauthorizing-paid-google-workspace-connection/33868/9 "2024-10-24T13:09:42Z")