How to Fix Google Drive 403 Error When Downloading Files in n8n

Below is a summary of the error you’re seeing and some troubleshooting suggestions:

Error Recap

Your workflow returns this error when trying to download files:

PLAINTEXTCopied
Forbidden - perhaps check your credentials?  

Request failed with status code 403

Even though you can list folder names and IDs, downloading files may require additional permissions/scopes within your Google Cloud project.

Possible Causes & Troubleshooting Steps

1. Missing/Insufficient OAuth Scopes
   • Ensure your OAuth credentials include the correct Google Drive scopes for file downloads.
   • For example, if you’re working with files, you might need to add scopes such as:

   PLAINTEXTCopied
   undefined

https://www.googleapis.com/auth/drive.readonly

• Double-check that the scope list provided in your credential (in n8n) is space-separated and correctly formatted.

2. **API Not Fully Enabled**  
• Verify that the Google Drive API (or the specific API needed for file downloads) is enabled in your Google Cloud Console project under APIs & Services > Library.  
• Sometimes one API (like listing files) might work with a lower-level permission while downloading requires additional access.

3. **Service Account Specific Issues**  
• If you’re using a Google Service Account, note that a similar error often appears if **Impersonate a User** isn’t enabled.  
• If applicable, refer to the documentation on [Service Account: Finish your n8n credential](#) for enabling domain-wide delegation and ensuring that the necessary APIs (like Drive) are included.

4. **File Access Restrictions**  
• Confirm that the files you’re trying to download aren’t restricted or require additional permissions. For example, files that aren’t shared with the authenticated user could cause a 403 error.

## Next Steps

- **Review Your Credential Setup:**  
Go to your Google Cloud Console and check the OAuth consent screen and the list of authorized scopes. Make sure you’ve added the complete set of scopes required for file downloads.

- **Test with a Minimal Workflow:**  
Create a simple workflow that only attempts to download a file. This can help isolate whether the issue is due to credential scopes/API settings or something else in the workflow.

- **Reauthorize After Changes:**  
If you modify scopes or enable additional APIs, reauthorize your Google connection in n8n so the new settings take effect.

Hopefully, these suggestions help you identify the missing component in your configuration and get your workflow downloading files as expected. If you need further assistance, please provide details about your OAuth configuration and the specific node setup used for file downloads.