I run into the typical problems integrating Gmail API, a day after I have set up an authorized my OAuth2 Client (using all steps described in various posts on how to set up a Google Workspace Oauth consent screen and client). The API call succeeds first time, but a day later I run into the 401 error telling me the token is not valid anymore. Authorizing the connection on a daily basis manually is not a feasible solution.
I would consider fetching the refresh token, storing this into a data store and before running the scenario with the HTTP/Oauth call to Gmail send along the new access token.
Is that feasible, and if yes, how would I get the refresh token from the initial request???
It seems most of the other Google Modules on make have this solved internally, BUT the Gmail Make Module has no “Make API calls” feature. Using HTTP OAUTH Request has also does not store the Access Token and Handle its refresh after it expires (currently 1hr), so one is left with the error message that the token is not valid after the first calls worked.
