This happens consistently on both general Google API credentials (used with Google Drive nodes) and with YouTube credentials (used with the YT node):
- I create a goole API credentials in Google’s API admin
- I create a n8n credential with the proper ClientID, Secret, callback URIs etc.
- Google Drive nodes use this credential successfully for 2-3 days then start failing
- See screenshot for fail message
- I create a new n8n credential with the exact same clientID and secret and it all works again… until it doesn’t.
- Repeat.
Seems like the credentials expire for some reason, and creating a new one with same API keys fixes it - but this is not sustainable for consistent use…
Thanks for any help
Noam
Did you publish the app?
You can publish to take it out of testing mode. You don’t have to verify the app or anything.
Let me know if it works.
1 Like
Thanks, yes tried it just this morning, will check to see if it doesn’t break in a few days - thanks a lot!!
1 Like
Hey @Noam_Josephides
How did it go? Is it working now?
seems like it’s working for the past 3 days, looking good so far, still checking 
Hey @Noam_Josephides how did it go?
so far it works on Drive. The YouTube node, however, started behaving in a similar way - breaking up every 2-3 days and rewquiring me to create another credential (with the exact same ClientID and secret!) and then it works again.
Anyhow, it’s manageable now so I’m good
Hey @Noam_Josephides
Maybe that’s because the YouTube credential was still using the old token?
Now that you’ve updated it, it shouldn’t behave like that anymore, if you are using the same Client ID as the one you used on Google Drive.
But anyways, if this topic is solved, can you please choose a reply as the solution so we can close this one?
