Google OAuth Bugs

Ask a question
1

Hi, i have sucessfully done a Google Oauth on multiple flows. However, recently, i noticed that i need to edit the Auth and then reauthorize it every time i want to run, making it a bit useless for automation. The minute i reauthorize, i see that it works just for that time and then stops again.

Thanks
Anto

2

Hi @ANTONY_RAPPAI - Happy to help! By default, Google’s API tokens expire after about an hour which is likely why you’re seeing that you need to re-authenticate more frequently. One way to increase the amount of time between token expirations is to request a longer expiration time of up to 12 hours by specifying the “expires_in” parameter when you authenticate.

You can read more about this here.

Let me know if you have any questions!

3

Ok, thanks for this. I’ve never had to do this before. For example, every once in a while, i have a roster update happening to some Google Classroom classes; for those i never had to reauthenticate, this seems less than even one hour. The worst part is that Parabola does not throw any errors. It shows as if the flow ran successfully without any errors.
I suspect there is something else as well. This same issue happened to me on another flow last week. It’s mostly to do with Google API authentication. That flow looks for new students in Airtble and tries to create new Google accounts. I thought it was running because it was successful, but the account was not created. Then I re-authenticated, and it worked.

In that link, you shared, how can we implement a refresh token?

4

Hi @Emory_Stainbrook , is there a way to implement this below

  1. Use Refresh Tokens: When you authenticate with OAuth2, you can request a refresh token in addition to an access token. The refresh token can be used to obtain a new access token when the current one expires, which can extend the expiration time of your authentication.
5

Hi @ANTONY_RAPPAI

You can implement a Refresh Token by completing the Refresh Token Request URL section when authorizing via OAuth 2.0.

Below is an example from the Google Ads API. The OAuth process is consistent throughout all of Google’s APIs:

Screenshot 2024-01-03 at 12.34.41 PM
Screenshot 2024-01-03 at 12.34.41 PM730×2446 127 KB

Toggle the “switch to custom settings” button if your authorization modal looks different.

  1. Start by adding your client_id, client_secret, and appropriate scope(s) for your API.

  2. In the Refresh Token Request URL section, add a grant_type body parameter. Set its value to refresh_token. Once complete select “Apply custom Oauth2 settings”.

  3. Finally, head back into your API step settings to ensure OAuth 2.0 is set to the correct Authentication type.

image

Let me know if that helps!