409 no_write_permission

(nothing important)

Hi DB-Des,

Thank you for your time. After going through client's account I found that they have not allowed the access to that space. So the issue is from the client side. 

Thanks

Hi DB-Des, 

Sure, let me provide you all the relevant information I believe could help you understand more context. 

- current n8n version: 1.98.2
I have attached a screenshot (https://ibb.co/bMTPbkdW) of my n8n workflow where I am storing my files in Dropbox, but it is giving me this error:

Your request is invalid or could not be processed by the service
path/no_write_permission/.

{
  "errorMessage": "Your request is invalid or could not be processed by the service",
  "errorDescription": "path/no_write_permission/.",
  "errorDetails": {
    "rawErrorMessage": [
      "409 - \"{\\\"error_summary\\\": \\\"path/no_write_permission/.\\\", \\\"error\\\": {\\\".tag\\\": \\\"path\\\", \\\"reason\\\": {\\\".tag\\\": \\\"no_write_permission\\\"}, \\\"upload_session_id\\\": \\\"pid_upload_session:ABIJdc_81xJkLlydgBwpH1e1Lm39wobdTSGJRFwe_aW0FV-Ulg\\\"}}\""
    ],
    "httpCode": "409"
  },
  "n8nDetails": {
    "nodeName": "Dropbox",
    "nodeType": "n8n-nodes-base.dropbox",
    "nodeVersion": 1,
    "resource": "file",
    "operation": "upload",
    "time": "7/22/2025, 2:26:06 PM",
    "n8nVersion": "1.98.2 (Cloud)",
    "binaryDataMode": "filesystem",
    "stackTrace": [
      "NodeApiError: Your request is invalid or could not be processed by the service",
      "        at ExecuteContext.dropboxApiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Dropbox/GenericFunctions.ts:48:9)",
      "        at processTicksAndRejections (node:internal/process/task_queues:105:5)",
      "        at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Dropbox/Dropbox.node.ts:906:21)",
      "        at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.78.1_encoding@0.1.13_zod@3.24.1_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1187:9)",
      "        at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.78.1_encoding@0.1.13_zod@3.24.1_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1536:27",
      "        at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.78.1_encoding@0.1.13_zod@3.24.1_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2100:11"
    ]
  }
}
My client's account is connected which is a team account, when they connected it was working fine but later some days it started to throw this error, then we reconnected the account and recreate the node and it got fixed, but it is throwing it again. I have also tried to fix it by recreating the node, but it didn't get fixed. 

If the issue was from permissions then why it was working before and if the issue was from token expiration or provocation then it should have sent a different error code and didn't have proceed this much. 

I am also attaching a screenshot (https://ibb.co/cKFw5GRn) of input and output of the node when it was executed:
file path in the node at that time: /Cathy Moyer/Lon/Clients - Lon/McMillian Security Systems/Alchemy/San Francisco/Certificates of Insurance/Outlook-aiogqfuv.png

I hope we would be able to resolve the issue as soon as possible, and wherever it could be coming from. 

Thank you

Hi hamza5​,

I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with:

• the name and version number of the platform and SDK/library you are using, if any
• the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s)
• 5-10 different 'X-Dropbox-Request-Id' response header values encountering the issue