Google OAuth verification rejected – drive.file vs spreadsheets scope (n8n)

Hi n8n team,

I’m using n8n with Google Sheets and going through Google OAuth verification.

Google has rejected the full Sheets scope (https://www.googleapis.com/auth/spreadsheets) and says my use case must work with drive.file. They also raised concerns because n8n is an AI-capable platform and want assurance that Google data is not sent to any AI services.

What I have already done:

- Removed all AI nodes and credentials

- Ensured no Google API data flows to any AI service

- Updated OAuth scopes to use only drive.file

- Updated Privacy Policy and Terms

- Created a clean demo workflow (create sheet + append row)

My questions:

1. Is drive.file the correct and recommended scope for n8n Google Sheets integrations?

2. Are there any known n8n limitations with drive.file for background automation?

3. Has anyone successfully passed Google OAuth verification for Sheets using n8n, and if so, any tips?

Any guidance or best practices from the n8n team or community would be appreciated.

Thanks in advance!

Hi @Aj_S,

I generally dont set any scopes when using google’s oauth option. I have never had this issue.

Where are you setting these scopes? On google console?

If so you can simply leave these blank