Overview
This node enables file operations over the Samba (SMB2) protocol, allowing interaction with SMB shares. The Download operation specifically downloads a file from a remote SMB share to be used within an n8n workflow.
Typical use cases include:
- Automating retrieval of files stored on network shares for further processing.
- Integrating legacy file shares into modern automation workflows.
- Downloading reports, logs, or documents from SMB servers for analysis or archival.
For example, you can configure this node to download a report file from a shared folder and then pass it to subsequent nodes for parsing or sending via email.
Properties
| Name | Meaning |
|---|---|
| Path | The full path of the file to download from the SMB share. Example: /public/documents/file-to-download.txt |
| Put Output File in Field | The name of the binary output field where the downloaded file will be stored. Default is data. |
Output
The node outputs the downloaded file as binary data attached to each item under the specified binary property name (default "data"). The binary data contains the exact contents of the downloaded file, enabling downstream nodes to access or manipulate the file content directly.
No additional JSON fields are added by default for the download operation; the main output is the binary file data.
Dependencies
- Requires a valid SMB2 server connection configured via credentials that provide authentication details.
- Uses temporary local storage to stream the downloaded file before attaching it as binary data.
- Relies on Node.js filesystem and streaming modules internally.
- No external API keys beyond SMB authentication are needed.
Troubleshooting
- Failed to create temporary file: Indicates issues creating a local temp file for streaming. Check disk space and permissions on the n8n host.
- Failed to download file: Commonly caused by incorrect file path, insufficient SMB permissions, or connectivity issues. Verify the full file path and user access rights on the SMB share.
- Binary data not found: If the binary property name is incorrect or missing, the node cannot attach the file. Ensure the property name matches the configured output field.
- Cleanup errors during temporary file removal are logged but do not stop execution.
If "Continue On Fail" is enabled, errors per item will be returned in the JSON error field instead of stopping the workflow.