Actions20
Overview
This node enables downloading files from Dropbox based on search results. It is designed to retrieve file content by specifying the file path obtained through a search operation. This is useful when you want to programmatically fetch files that match certain criteria without manually browsing folders.
Common scenarios include:
- Automatically downloading files found via a search query for further processing.
- Integrating Dropbox file retrieval into workflows where files are identified dynamically.
- Fetching specific files by path after locating them with other operations.
For example, after searching for all PDF documents in a folder, this node can download each matching file's content for use in subsequent workflow steps like analysis or storage elsewhere.
Properties
| Name | Meaning |
|---|---|
| File Path | The full path of the file to download from Dropbox (e.g., /path/to/file.jpg). Required. |
| Return Format | Format of the downloaded file content: either Base64 encoded string or raw Buffer. |
| Output Field | The name of the field in the output JSON where the downloaded file content will be stored. |
Output
The node outputs a JSON object containing metadata about the downloaded file and the file content itself under the specified output field name.
Output fields include:
resource: Always"file".operation: Always"download".path: The file path used for download.metadata: Metadata returned by Dropbox about the file.size: Size of the downloaded file in bytes.content_type: Content type inferred from the file hash or set as"application/octet-stream".<outputField>: The actual file content, either as a base64 encoded string or a buffer depending on the selected return format.
If the return format is base64, the file content is a base64 string; if buffer, it is a binary buffer.
Dependencies
- Requires an active OAuth 2.0 authentication token for Dropbox API access.
- Uses Dropbox API endpoints for file download (
https://content.dropboxapi.com/2/files/download). - Needs proper n8n credentials setup with OAuth 2.0 for Dropbox.
- Network connectivity to Dropbox API endpoints.
Troubleshooting
- Invalid or expired OAuth token: The node attempts to refresh the token automatically but may fail if refresh credentials are invalid or missing. Ensure OAuth credentials are correctly configured and valid.
- File not found error: If the specified file path does not exist or is incorrect, Dropbox API will return an error. Verify the file path is correct and accessible.
- Permission errors: Insufficient permissions on the Dropbox account or app may cause failures. Confirm the OAuth token has required scopes.
- Large file handling: Downloading very large files might cause memory issues depending on workflow environment. Consider chunking or alternative approaches if needed.