Connections requiring frequent reauthorization

Getting Started
, ,
1

Hi! New to make.com. I’ve created a scenario and I’ve run it successfully. However, some of my connections keep requiring reauthorization:

Google (Paid): I first encountered the issue using my business account. After a while, I switched to personal (free) account to see if that would help.

Google (Free): worked at first but a few hours later I encountered the same problem.

Webflow: The same issue as both free and paid Google accounts.

The other issue is that reauthorizing doesn’t even work. I go through the steps of granting permissions and then the reauthorize button reappears almost immediately. To get the scenarios to run, I’ve had to delete the connection and then connect again.

Any help would be SO appreciated!!!

2

For Google personal connections, you’ll need to create a private app on the Google cloud platform to connect to.

Then when creating a connection on Make, you’ll expand the Advanced Settings, insert the app client id and secret BEFORE clicking the sign in button.

This will avoid the frequent reauthorize bit. I have never needed to reauthorize my Google connections.

Instructions have been provided in the help center, or you can search my previous posts on this forum for @samliew Google OAuth GCP

samliew – request private consultation

Join the unofficial Make Discord server to chat with us!

4

Thank you so much for your response. I do have a paid google account which seems like it should work without doing that but if it comes to it, I will give it a shot.

Thank you again!

5

No, a paid personal account is still a personal account.

You will still need to use the private GCP app connection method.

samliew – request private consultation

Join the Make Fans Discord server to chat with other makers!

6

@samliew, can I ask you if you run your GCP Gmail Oauth project to connect a personal Gmail as a test or production project in GCP?

In test mode, I get asked to reauthorise the refresh token every 7 days

because sending mail is considered a sensitive scope by GCP there seem to be lots of hoops to jump through to make this sort of project a production project.

I’m trying lots of different things with a test project but I always get 403 errors after 7 days. its a bit difficult to trouble shoot because once the refresh token is renewed manually it works perfectly for 7 days!

Thanks

7

Welcome to the Make community!

Yes, personal Gmail, GCP production mode, not verified.

Basically all my screenshots are of my own GCP set-up.

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

— @samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

1 Like
8

Hi Sam. 7 days after converting my GCP project to production but not verified I’ve kicked off again. Make does not action the refresh token in the Gmail connector. I will try creating a custom integration like this one and see if that works. HTTP OAuth2 Module - How to get Refresh Token for Google APIs - #5 by Shawn

1 Like