I have a few scenarios where I take my WordPress blog post url’s and submit them to Google’s index using the API. This works for a few attempts but I noticed that after some time (or maybe the amount of attempts) I get an authorization response from Google and I have to go into my Make connection and edit the connection (1) and then reauthorize (2) be selecting my Gmail account. I should note I’m not making any changes to the connection but unless I edit first I cannot reauthorize.
I’m hoping someone has experienced this and has a solution.
Here are all the known 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.
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 respective APIs for your custom app in Google Cloud.
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:
In particular, I’m not quite sure how to access the “refresh token” when we are setting up the initial connection – because there is no “refresh token” yet!
I’ve bookmarked this topic so hopefully we can find a resolution – there have been a number of questions about this issue on the forums, but nobody has been able to solve this yet. I’m linking the old issues here so that the thread starters will get notified, perhaps one of them might have already solved this.
This also seems like something that should be handled by any OAuth integration automatically. You can try contacting Make support to see if the OAuth2 connection can be automatically updated with the refresh token. Directly contacting support can often lead to a faster resolution. They have access to internal tools and resources, which allows them to investigate more thoroughly than what we have access to.
If you manage to solve this issue, I’d love to hear about it! Sharing your solution on the forum can help others facing similar problems.
You are correct. It does seem to be an issue with how Make.com handles the refresh token. I reached out to the make.com customer support and though they were very helpful in exploring different angles, I managed to get a custom app to work sooner and properly handle the refresh tokens (for Jobber).
@Thomas_Gaillard was also very helpful along the way and may be able to shed some light.
in your screen, you can see, verification required.
And if you look into the screen about the requirements, you will see a demo
video is needed by google.
@Shawn I have issues with tokens not refreshing as well. To be honest I thought this was me, but it seems like a lot of people have issues with this. Do you have any information at all as to how you approached the solution you came to? Screenshots that you can share, etc.?
This is a big blocker for some of the solutions we’re trying to build with Make, so a solution would be a godsend to be honest!
Hi @Bob_Balm,
I have it on my list to do a little tutorial with screenshots. If you have a particular issue with a custom app you are setting up please set up a question with screenshots of what you have and I may be able to help get you over the hump.
