# Redirect\_uri\_mismatch when connecting to Google Workspace Gmail

**URL:** <https://community.make.com/t/redirect-uri-mismatch-when-connecting-to-google-workspace-gmail/95552>\
**Category:** Beginner Questions\
**Tags:** gmail, api\
**Created:** [November 5, 2025, 4:30pm UTC](https://community.make.com/t/redirect-uri-mismatch-when-connecting-to-google-workspace-gmail/95552 "2025-11-05T16:30:42Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mic-sir](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@mic-sir](https://community.make.com/u/mic-sir)\
**Post date:** [November 5, 2025, 4:30pm UTC](https://community.make.com/t/redirect-uri-mismatch-when-connecting-to-google-workspace-gmail/95552/1 "2025-11-05T16:30:42Z")

</div>

Hey there.

We are trying to connect to our Google Workspace. I know that there are several posts out there which all have the same issue and they always get it running by the description of **samliew.**

We followed everything by the book like samliew described here:

> [@Redirect uri mismatch error](https://community.make.com/t/redirect-uri-mismatch-error/29095):
>
> Im trying to connect my Gmail account, so I followed the steps in this link [https://www.make.com/en/help/connections/connecting-to-google-services-using-a-custom-oauth-client?\_gl=1\*1pho9ep\*\_ga\*NzA4MTA2NTM0LjE3MDkyMjQ4NzQ.\*\_ga\_MY0CJTCDSF\*MTcwOTIyNDg3NC4xLjEuMTcwOTIyNjE5MC42MC4wLjA.](https://www.make.com/en/help/connections/connecting-to-google-services-using-a-custom-oauth-client?_gl=1*1pho9ep*_ga*NzA4MTA2NTM0LjE3MDkyMjQ4NzQ.*_ga_MY0CJTCDSF*MTcwOTIyNDg3NC4xLjEuMTcwOTIyNjE5MC42MC4wLjA.), I added the following URI [https://www.integromat.com/oauth/cb/google-restricted/](https://www.integromat.com/oauth/cb/google-restricted/) as shown in the video but I get the following error “Error 400: redirect\_uri\_mismatch”. what could be the issue? [Screenshot 2024-02-29…

But in our case it just won’t work and I don’t know what to do next. We still get the error

> Error 400: redirect\_uri\_mismatch
> 
> You cannot sign in to this app because it does not comply with Google’s OAuth 2.0 guidelines.
> 
> If you are the app developer, register the redirect URI in the Google Cloud Console.
> 
> Details:  
> redirect\_uri=[https://www.make.com/oauth/cb/google-email](https://www.make.com/oauth/cb/google-email) flowName=GeneralOAuthFlow

These are our added authorized redirect URIs:

 ![urls](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/8/e/8e4d9c46f1968efff662b97c39e18919133e4aca.png)

I even added the one from the Error but no luck.

What am I missing?

Does the project need to be “Published” or can it also be in “Testing”?

Greetings,

Michael

---

<div class="post-metadata">

**Author:** ![mszymkowiak](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mszymkowiak/32/41436_2.png) [@mszymkowiak](https://community.make.com/u/mszymkowiak)\
**Post date:** [November 5, 2025, 5:36pm UTC](https://community.make.com/t/redirect-uri-mismatch-when-connecting-to-google-workspace-gmail/95552/2 "2025-11-05T17:36:17Z")

</div>

Hello,

Why is your point about using custom OAuth if you are using Google Workspace?

It is mandatory for personal Gmail accounts.

Regarding your question about testing vs. published:

> Testing: If you keep your project in the Testing status, you will be required to reauthorize your connection in Make every week. To avoid weekly reauthorization, update the project status to In production.
> 
> In production: If you update your project to the In production status, you will not be required to reauthorize the connection weekly. To update your project’s status, go to the Google Auth Platform, the Audience section, and click Publish app.

Source: [Connect to Google services using a custom OAuth client - Help Center](https://help.make.com/connect-to-google-services-using-a-custom-oauth-client)

---

<div class="post-metadata">

**Author:** ![mic-sir](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@mic-sir](https://community.make.com/u/mic-sir)\
**Post date:** [November 6, 2025, 11:38am UTC](https://community.make.com/t/redirect-uri-mismatch-when-connecting-to-google-workspace-gmail/95552/3 "2025-11-06T11:38:24Z")

</div>

What do you mean exactly? We followed the documentation for [Google Workspace Admins](https://apps.make.com/google-g-suite) and there the article says:

> In order to use OAuth2 with your Google apps, you need to create your own project and a custom OAuth client in Google Cloud Console. This is useful for connecting restricted Google services, like Google Drive or Gmail, to Make.
> 
> The following procedure is intended for:
> 
> - **Personal use** ([gmail.com](http://gmail.com) und [google.com](http://google.com) users)
> 
> - **Organizational use** (Internal use within a business or other organization_Google Workspace (formerly GSuite)_ users that prefer to use a custom OAuth client)

So we presumed that this is the way to connect to our Google Workspace…

---

<div class="post-metadata">

**Author:** ![mszymkowiak](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mszymkowiak/32/41436_2.png) [@mszymkowiak](https://community.make.com/u/mszymkowiak)\
**Post date:** [November 6, 2025, 2:39pm UTC](https://community.make.com/t/redirect-uri-mismatch-when-connecting-to-google-workspace-gmail/95552/4 "2025-11-06T14:39:01Z")

</div>

> [@mic-sir](#):
>
> The following procedure is intended for: […] **Organizational use** […] that **prefer** to use a custom OAuth client

That’s the key- prefer 🙂

If you don’t have any extra security policies requiring you to use only custom apps internally- as Workspace users you can use modules out-of-the-box with [Make.com](http://Make.com) Google Connection.

Just add connection name, click “Sign in with Google”, follow oAuth flow and… you should be good to go.

In case of any problems- fell free to ask. If you will solve your problem- mark solution- it will help others.

Have a nice day!

---

<div class="post-metadata">

**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:** [November 6, 2025, 10:47pm UTC](https://community.make.com/t/redirect-uri-mismatch-when-connecting-to-google-workspace-gmail/95552/5 "2025-11-06T22:47:39Z")

</div>

Welcome to the Make Community!

> [@mic-sir](#):
>
> We followed everything by the book like samliew described here:

Those instructions are already outdated! [Try searching for a later post!](https://community.make.com/search?context=user&context_id=samliew&q=Google%20oauth%20order%3Alatest_topic&skip_context=false)

Hope this helps! Let me know if there are any further questions or issues.

— @samliew

---

<div class="post-metadata">

**Author:** ![mic-sir](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@mic-sir](https://community.make.com/u/mic-sir)\
**Post date:** [November 7, 2025, 2:08pm UTC](https://community.make.com/t/redirect-uri-mismatch-when-connecting-to-google-workspace-gmail/95552/6 "2025-11-07T14:08:33Z")

</div>

It was a mistake on our part. We thought we could use Google Workspace groups in the same way as personal Google users. But apparently that doesn’t work or isn’t supported. Thank you for the help anyway.

---

<div class="post-metadata">

**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:** [November 21, 2025, 2:12pm UTC](https://community.make.com/t/redirect-uri-mismatch-when-connecting-to-google-workspace-gmail/95552/7 "2025-11-21T14:12:04Z")

</div>


