Fix: n8n Google Drive API 403 error

    A Google Drive API 403 in n8n is caused by the wrong Google Cloud project, a disabled API, or stale OAuth consent. Check those in order and reauthorize the credential.

    Last updated 2026-09-21~5 min read
    n8nGoogle Drive APIGoogle OAuth 2.0Google Cloud Console

    Last updated: 2026-09-03 · Tested on: n8n 1.x with Google Drive API OAuth 2.0 · Read time: ~4 min

    Symptoms — what you're seeing

    • An n8n Google Drive node fails with a 403 response when it lists, uploads, downloads, or watches files
    • Google Sheets or Gmail nodes work with the same Google account, but a Drive operation fails
    • Google Cloud reports that the Drive API has not been used in the project or is disabled
    • The OAuth credential connects successfully, but the first Google Drive request is rejected
    • A workflow that worked in one n8n environment returns 403 after the credential is recreated or moved to another environment

    Why this happens

    A successful OAuth connection does not prove that the Google Drive API is enabled. OAuth authenticates the Google account. Google Cloud still checks whether the API, project, scopes, and account permissions allow the requested Drive operation.

    1. The Drive API is disabled in the OAuth project. Google Sheets API and Google Drive API are separate services. A working Google Sheets Trigger does not automatically enable Drive access. This is the most common cause of a first-use 403.

    2. You enabled the API in the wrong Google Cloud project. The project selected in Google Cloud Console must be the project that owns the OAuth client used by the n8n credential. Enabling Drive in a different project has no effect.

    3. The credential has stale consent or insufficient scopes. If you changed the requested scopes, changed the OAuth consent screen, or replaced the client ID, the token stored by n8n may not contain the permissions required by the Drive node. Reconnecting the credential forces Google to issue a new token.

    4. The OAuth app is still in testing. For an external OAuth app in testing, the Google account must be listed as a test user. A missing test user normally produces an OAuth consent error rather than an API error, but it often appears during the same setup attempt.

    5. The Google account can authenticate but cannot access the file. A valid token does not grant access to every Drive file. Shared drives, files owned by another Workspace account, domain policies, and insufficient folder permissions can all block a specific operation.

    The fix, step by step

    1. Identify which n8n credential the failing node uses. Open the Google Drive node and note the selected credential. Do not assume it is the same OAuth project or account used by your Google Sheets node.
    2. Open the matching Google Cloud project. In Google Cloud Console, go to APIs & Services > Credentials and find the OAuth client used by that n8n credential. Copy the project ID and keep that project selected while checking the API settings.
    3. Enable the Google Drive API in that project. Go to APIs & Services > Library, search for Google Drive API, open the service, and select Enable. Also leave any API already required by the workflow enabled, such as Google Sheets API or Gmail API.
    4. Check the OAuth consent screen. Confirm that the app is configured for the correct audience. If the app is in testing, add the Google account used by n8n under test users. Check that the account and Workspace domain are allowed to use the app.
    5. Reconnect the n8n credential. In n8n, open Credentials, select the Google OAuth2 credential, and use the reconnect or sign-in action. Complete the consent screen and grant the Drive permission requested by the node. If n8n is using a custom OAuth client, confirm that its redirect URI still matches the n8n credential configuration before reconnecting.
    6. Run a minimal Drive test. Create a temporary Google Drive node that lists files or gets metadata for a file you own. Use a small result limit. If this works, the API and credential are valid; move on to the original node's folder, shared-drive, or file configuration.
    7. Check the target file and folder permissions. Open the file in Google Drive with the same account used by n8n. For a shared drive, confirm that the account has the required role and that the node is configured for the correct drive or folder. A credential that can list its own files may still fail on a restricted shared-drive file.
    8. Retest the complete workflow. Execute the Drive node first, then run the workflow with the real trigger. If the workflow also calls Gmail or Sheets, inspect each node separately so a later 403 is not mistaken for a Drive failure.

    Stuck on this for more than 30 minutes? Book a 30-min call. I’ll inspect the n8n credential, Google Cloud project, scopes, and failing node with you, then either fix it on the call or scope what it will take. No upsell, no decks.

    Common variations

    • Google Sheets works, but Google Drive fails. Enable the Drive API separately. Sheets API access does not include Drive API access.
    • The error appears after moving from local n8n to a server. The server may use a different credential, OAuth client, redirect URL, or environment variable. Compare the credential selected by the node in both environments.
    • The node works for personal files but not shared-drive files. Check the account's shared-drive membership, the target folder permission, and any Workspace administrator restrictions.
    • The credential connects but Google returns an OAuth consent error. Check the OAuth app's test-user list and consent-screen configuration before debugging the Drive node itself.
    • The workflow fails only when creating or uploading a file. Listing metadata can require less access than writing. Check the folder's write permission and the scope granted during reconnection.

    Once the Google credential is fixed, the next failures usually move downstream: an OpenAI request can hit a 429 rate limit, or a scheduled workflow can run at the wrong local time because of the n8n schedule timezone. Debug each node's request and output separately.

    When this isn't the issue

    If the Google Drive API is enabled, the credential has been reconnected, and a minimal test still fails, check these forks:

    • The 403 names a specific file or folder. Open that resource using the OAuth account and verify its sharing, folder inheritance, shared-drive membership, and Workspace policy.
    • The error occurs only with a shared drive. Confirm that the n8n Google Drive node supports the operation against that drive and that the selected account has permission to create or modify content there — the exact node operation and shared-drive option can differ between n8n versions, so confirm both against your installed version.
    • The error appears only after changing OAuth scopes. Delete or reconnect the affected n8n credential so Google issues a token with the current scopes. A browser login succeeding does not update an old token automatically.

    Related pages

    Continue debugging adjacent n8n failures with the n8n schedule trigger timezone fix, the n8n OpenAI 429 rate limit fix, and the n8n Simple Memory node error fix.

    Stuck on this for more than 30 minutes? Book a 30-min call. I’ll inspect the workflow with you and either fix it on the call or scope what it will take. No upsell, no decks. · Email Basit

    Next: fix n8n OpenAI 429 rate limit errors →

    Need this workflow customized or debugged? Book a 30-min scope call →

    Stuck configuring this workflow?

    I build and fix n8n workflows for agencies and SaaS teams. 30-minute scope call — bring the problem, leave with an estimate.

    Related pages