What are you trying to achieve?
Hi everyone,
I’m trying to set up the Google My Business – Watch Reviews module on Make.com, but I’m stuck with an authentication issue.
I’ve already created the OAuth 2.0 Client ID in Google Cloud Console, and I’ve added both of the following URIs under Authorized redirect URIs:
https://www.make.com/oauth/cb/google
https://www.integromat.com/oauth/cb/google/
However, I still get the following error when trying to connect my Google account:
Error 400: redirect_uri_mismatch
I double-checked that the URIs are correct but still the problem persist.
Any ideas on what might be wrong or what else I need to configure?
Thanks in advance! 
Steps taken so far
Already tried both URIs above
Client ID and Client Secret correctly inserted
Welcome to the Make community!
These aren’t all the required URLs. Also, https://www.make.com/oauth/cb/google is not the same as https://www.make.com/oauth/cb/google/ - you need to insert both!
See below for more information.
How to Connect and Use Google APIs in Make!
0. Prerequisites
1. Enable Google APIs
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-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-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:
Related Topics:
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!
First of all, I want to sincerely thank you for your detailed and prompt response. It really made me feel supported and cared for.
I tried to follow all the steps you meticulously shared, but unfortunately I still can’t break through the same wall: “Error 400: redirect_uri_mismatch.”
No matter what I do, the app remains blocked.
Every time I go to the OAuth consent screen, the page refreshes and redirects me somewhere else, and the interface doesn’t look anything like what you showed in your screenshot. I did find a “PUBLISH APP” button and a “CONFIRM” button at some point, but then Google forces me to request an app verification, asking for things like a public website and a privacy policy page that I really don’t need at all.
All I want is to scrape the reviews from my own business.
Why does this have to be so difficult?
Thanks again for your help. I truly appreciate your time and guidance, even if I’m still stuck for now.
That isn’t true. The verification step is optional as you are the only user using the GCP app.
Please take screenshots of your Redirect URI list, taking care not to display the client ID & secret.
Please click on the “error details” link in the OAuth screen (where you see the “redirect_uri_mismatch” error), and take a screenshot of it.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
