Introduction
Automation platforms like n8n make it simple to connect different apps and automate workflows. One of the most popular integrations is with Google Drive, which allows users to automatically create folders, upload files, and manage documents.
To connect Google Drive with n8n, there are two common authentication methods:
- OAuth – Works with your personal or organizational Google account.
- Service Accounts – Work like a “robot account” for background or backend automation.
However, many users face a common issue:
- Create Folder works with a Service Account.
- Upload File works with OAuth.
- But Upload File fails with a Service Account, showing this error:
Problem in node ‘Google Drive’
Request failed with status code 403
This article explains why this happens and the step-by-step fix.
Why the 403 Error Happens
A Service Account in Google Cloud is like a separate Google user with its own private Drive.
- When you run Create Folder, the folder is created inside the Service Account’s own Drive.
- When you try Upload File, the target is usually your personal or organizational Drive. Since the Service Account has no access there, Google Drive blocks the upload, returning a 403 Forbidden error.
How to Fix the 403 Error
The solution is to treat the Service Account like any other Google user by sharing the folder with it.
Step 1: Get the Service Account Email
- Go to Google Cloud Console → IAM & Admin → Service Accounts.
- Copy the email (looks like: xxxx@project-id.iam.gserviceaccount.com).
Step 2: Share the Folder
- Open Google Drive.
- Right-click the folder you want to use → Share.
- Add the Service Account email.
- Set permissions to Editor.
Step 3: Use the Folder ID in n8n
- Copy the folder ID from the Google Drive folder URL.
- Paste this ID into the Upload File node in n8n.
✅ Done – now the Service Account can upload files successfully.
Best Practices for Google Drive + n8n
- Use Service Accounts for backend or server-based automations.
- Use OAuth for user-specific workflows.
- Always check that the Service Account has Editor access.
- Use Folder IDs instead of names to avoid mismatches.
- Add error-handling in n8n to capture 403 errors and send alerts.
Conclusion
The 403 error when uploading files with a Service Account isn’t a bug – it’s a permissions problem. By sharing your target folder with the Service Account and granting Editor access, you unlock the full potential of Google Drive automation in n8n.
With this fix, you can confidently use Service Accounts for secure, scalable, and fully automated workflows.
