What is your goal?sending emails in gmail by connecting it to the make.com
What is the problem & what have you tried?problem occurred when making connection between make.com and gmail
Error messages or input/output bundlesaccess blocked
Screenshots (scenario flow, module settings, errors)Hey @Vighnesh_Javir ,
Have you checked this guide out and can you double-check if everything is setup as per the guide and test if you still see this error after doing so?
Hope this helps.
Hello,
While I am not totally sure if this is the issue you are facing, connecting a personal email to Make is a little bit different than a standard Make connection.
You will need to setup a new project in your Gmail account and connect Make’s URL to it.
Below is a blog post we created to explain the process of connecting an email account.
I hope this helps clarify the issue you are having.
This isn’t a Gmail permission issue — it’s an OAuth redirect mismatch.
The key line in your screenshot is:
Error 400: redirect_uri_mismatch
That means:
Google received the auth request
but the redirect URI sent by Make doesn’t match what’s registered in the Google Cloud OAuth settings
This usually happens when:
a custom Google OAuth client is used and the redirect URI isn’t updated, or
the connection was created earlier and Google’s OAuth config was changed/reset
At a high level, the fix is to make sure the exact redirect URI Make expects is allowed in the Google Cloud Console for that OAuth client.
If you want, I can outline where to find the correct redirect URI and how to reset the connection cleanly.
Welcome to the Make community!
Please see Step 2: Create OAuth Client below.
Make sure you can sign in to Google Cloud Console with this.
Follow this main help centre guide on How to set up a custom OAuth 2.0 custom app in Make.
Search for the relevant Google API here: https://console.cloud.google.com/apis/library
Direct Link: https://console.cloud.google.com/apis/credentials
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
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/- 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!
Direct Link: https://console.cloud.google.com/apis/credentials/consent/edit
Insert make.com and integromat.com
Fill in other required fields
Click “Save and Continue”.
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
Step through until you reach back to the dashboard
At the last step/page, click “BACK TO DASHBOARD” instead of “Prepare for Verification”
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
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:
Insert the GCP app client ID and secret here BEFORE clicking “Sign in”
(Gmail example)
OR,
You need a “Authorize Parameters” key of redirect_uri with the above Make OAuth2 callback URL.
Related Topics:
— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!
yes please outline where to find correct redirect URL.
Have you seen @samliew’s reply? All the info is in there.
I said…
— @samliew
