Google Calendar OAuth - refresh token

[danielrubak]

Hello! I have a problem with the Google Calendar node because this node is using Google OAuth credentials that expire every 7 days (I ran the project in test mode on Google Cloud, I cannot switch to production mode because I use http for connection validation).
I found a lot of refresh token topics and I wonder if it is possible to apply these solutions in some way to the built-in Google Auth credentials:

No refresh Token (Google Admin SDK API)

Hello n8n community, I use Google SDK API to get users quota of my user in GSuite. I have a problem with the refresh token in the OAuth2 with this setup: [Capture d’écran 2021-05-07 à 09.28.19] After initial connection i get the data and my N8N Workflow work but after an hour i get the “No refresh Token” error. I tried the G Suite Admin node but i didn’t get the needed informations. Opening the credentials and reconnecting will give me a new valid token for another hour. Anyone else en…

Google Calendar OAuth2 API token expiring every once in a while

The title kind of explains everything. I use the Google Calendar OAuth2 API and I just have to re-authenticate every once in a while (by pressing the ‘reconnect’ button in the Credentials editing screen), otherwise it will just error out. The error it encounters is: “Token has been expired or revoked”. Does anyone know a way to fix this (like if there is a way I can either extend the expiry date of the token, or if there is a way for it to automatically renew it)?

Right now, I have to manually refresh the token every 7 days and it’s annoying. Hope there is a way to fix this problem.

[MutedJam]

Hi @danielrubak, seeing this is happening every seven days for you, I suspect this isn’t a problem with n8n not attempting the refresh but rather with Google not allowing the refresh. You might need to publish the OAuth2 client you have registered with Google, as for test users the authentication will expire after seven days as per Google’s documentation:

Authorizations by a test user will expire seven days from the time of consent.

From testing this myself it seems Google doesn’t enforce this if the authenticating user is identical with the GCP project owner, but this might change at any time.

So to avoid running into this you would need to publish your application or consider using a Google Workspace account which would allow you to create an Interal OAuth client only accessible to users within your organization.