How to Fix Google OAuth Credentials Expiring After 7 Days in n8n
If you're using a self-hosted n8n instance and encountering issues with Google OAuth credentials expiring every 7 days due to your app not being validated by Google, here's a straightforward fix. By adjusting the consent screen settings, you can bypass Google's extended validation process and make your app production-ready.
Steps to Fix the Issue:
-
Access Google Cloud Console:
- Log in to your Google Cloud Console.
- Navigate to the project associated with your n8n workflows.
-
Go to the OAuth Consent Screen:
- In the left-hand menu, go to APIs & Services > OAuth Consent Screen.
-
Remove the Logo:
- If you've uploaded a logo for your app, remove it from the consent screen settings. The logo triggers additional validation requirements that prolong the process.
-
Publish the App:
- Scroll down to the bottom of the consent screen page and click Publish App to move your app from Testing to Production.
-
Confirm the Changes:
- Ensure that your app status is now listed as In Production. This prevents your OAuth tokens from expiring after 7 days.
-
Test the Integration:
- Go back to your n8n workflows and ensure that Google services are properly integrated and the credentials remain active beyond the 7-day limit.
By removing the logo and publishing your app, you can avoid the cumbersome app verification process while ensuring that your Google OAuth credentials remain valid for longer durations.