Google Drive - Copy Operation - “Forbidden - perhaps check your credentials”

I have an active workflow that copies a template from google drive into a specified folder, then pre fills that template in the next step. On the Copy File and Copy File1 node, I am using the copy operation.

It was previously working for us. We have made no changes, but it is now giving “Forbidden - perhaps check your credentials”, with no other explanation.
Moreover, for one template first Copy File fails, and for other template in the same folder, first Copy File works, but second Copy File1 fails. It is happening on a random basis. Has anyone seen this behaviour?
It is happening randomly on Copy and Copy1 nodes.

Error snippet attached below


Forbidden - perhaps check your credentials?

This file cannot be copied by the user.

Error details

From Google Drive

Error code

403

Full message

Request failed with status code 403

Error data

{ “error”: { “code”: 403, “message”: “This file cannot be copied by the user.”, “errors”: [ { “message”: “This file cannot be copied by the user.”, “domain”: “global”, “reason”: “cannotCopyFile” } ] } }

Other info

Node type

n8n-nodes-base.googleDrive

Node version

3 (Latest)

n8n version

1.114.4 (Self Hosted)

Time

01/12/2025, 20:33:17

Stack trace

NodeApiError: Forbidden - perhaps check your credentials? at ExecuteContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1365:9) at processTicksAndRejections (node:internal/process/task_queues:105:5) at ExecuteContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1737:11) at ExecuteContext.googleApiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_afd197edb2c1f848eae21a96a97fab23/node_modules/n8n-nodes-base/nodes/Google/Drive/v2/transport/index.ts:54:11) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_afd197edb2c1f848eae21a96a97fab23/node_modules/n8n-nodes-base/nodes/Google/Drive/v2/actions/file/copy.operation.ts:123:19) at ExecuteContext.router (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_afd197edb2c1f848eae21a96a97fab23/node_modules/n8n-nodes-base/nodes/Google/Drive/v2/actions/router.ts:29:26) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_afd197edb2c1f848eae21a96a97fab23/node_modules/n8n-nodes-base/nodes/Google/Drive/v2/GoogleDriveV2.node.ts:25:10) at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1091:8) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1272:11) at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1673:27


  • n8n version: 1.114.4

  • Database (default: SQLite):

  • n8n EXECUTIONS_PROCESS setting (default: own, main):

  • Running n8n via (Docker, npm, n8n cloud, desktop app): self hosted

Hey! That random 403 error usually means Google Drive permissions changed or the service account lost access. Check if the files or parent folder permissions got modified—sometimes shared drives or org policies can block copying even if you had access before. Try re-authenticating your Google credentials in N8n, and verify the service account or OAuth user still has edit rights on both the template files and destination folders. Also worth checking if Google imposed new API restrictions on your account.