Dropbox Proxy

Communicates with Dropbox via a Cloudflare worker

Actions11

Overview

This node acts as a proxy to interact with Dropbox file storage via a Cloudflare worker. It enables various file and folder operations such as copying, moving, deleting, uploading, downloading, listing contents, and creating folders in a Dropbox account.

Common scenarios where this node is beneficial include automating file management workflows in Dropbox without directly handling Dropbox API complexities or authentication. For example, you can automate backing up files by copying them to another folder, move files after processing, or download files for further use in other systems.

Practical examples:

  • Copy a file from one Dropbox folder to another as part of a backup routine.
  • Upload a new file encoded in Base64 to Dropbox.
  • Download a file from Dropbox to process its content downstream.
  • List the contents of a Dropbox folder to trigger actions based on file presence.

Properties

Name Meaning
Path The path of the file or folder to operate on (e.g., /Documents/report.pdf). Required.
Destination Path The target path for copy or move operations (e.g., /Archives/report_backup.pdf).

Output

The output is an array of items, each containing a json property with the response data from Dropbox API calls. The structure varies depending on the operation:

  • For most operations (copy, move, delete, create folder, list folder), the JSON contains metadata or confirmation objects returned by Dropbox.
  • For the downloadFile operation, the output includes a binary property named data containing the downloaded file's binary content, prepared for further n8n processing, alongside a JSON object confirming success and the file path.

Dependencies

  • Requires an API key credential to authenticate requests to the Dropbox proxy service hosted on a Cloudflare worker.
  • The node expects two credential parameters: a worker URL and an access token.
  • No direct Dropbox credentials are used; all communication goes through the proxy endpoint.

Troubleshooting

  • Missing credentials error: If the worker URL or access token is not set or invalid, the node will throw an error indicating missing credentials. Ensure these are configured correctly in the node credentials.
  • File content required for upload: When performing an upload operation, if the Base64-encoded file content is empty or missing, the node throws an error. Provide valid Base64 content.
  • Unsupported operation: If an unsupported operation name is provided, the node throws an error. Use only the supported operations listed in the properties.
  • HTTP request failures: Network issues or invalid paths may cause HTTP errors. Check the validity of paths and network connectivity to the proxy service.

Links and References

Discussion