Hello,
In the Google Drive OAuth2 API, after saving the client secret from Google Cloud, the client secret constantly changes to “__n8n_BLANK_VALUE_xxxxxxx.”
Why does this happen? And how can I stop it?
This is an issue in n8n in can also occur locally also and not configure any Google nodes with OAuth2 API or Service Account
Hi there! When adding any secrets/tokens to credentials in n8n we want to make sure that they are stored securely. For that reason, they are encrypted before storing them in the database, and you cannot see them when editing the credentials after you’ve added them. The __n8n_BLANK_VALUE_xxxxxxx value you are seeing is just a placeholder that is displayed in the UI, but the actual secret is properly stored and used when calling the service. If you need to access your secrets after adding them to credentials in n8n, make sure to use other dedicated software. Hope this clears up some confusion!
2 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.