Now I have an error 431 in google drive node, when I make the credential and make it by Custom OAuth, and make all steps right in Google Cloud, I get the following msg Error 431
Hi @mariam202 
, I moved this to the Questions category so it gets better visibility for troubleshooting. You’ll likely get more targeted help here 
Thank you I have solved the Google Drive Credentials as It became more easier than before without going to Google Cloud
@Miliaga Thank you
The 431 error in the Google Drive node usually means the request headers are too large. In this case, it is most likely caused by browser cookies/session data during the Google OAuth flow, not necessarily by a wrong Google Cloud setup.
To fix it:
Open n8n in an incognito/private window.
Clear cookies for your n8n domain and Google.
Delete the broken Google Drive credential in n8n.
Create the Google Drive OAuth credential again.
Copy the Redirect URL from n8n and paste it exactly into Google Cloud.
Make sure your self-hosted n8n has the correct public URLs:
Environment
N8N_HOST=n8n.yourdomain.com
N8N_PROTOCOL=https
WEBHOOK_URL=https://n8n.yourdomain.com/
N8N_EDITOR_BASE_URL=https://n8n.yourdomain.com/
N8N_PROXY_HOPS=1
After that, restart n8n and reconnect the Google Drive credential.
In most cases, if the OAuth configuration is correct and the error is 431, cleaning the browser session or using incognito solves the problem.
It usually happen due to the browsers cookie or cache, try using the incognito mode, or try clearing the browser cookie specifically for the n8n instance