Actions40
- Job Actions
- Account Hierarchy Actions
- Cryptography Actions
- Customer Hierarchy Actions
- File Explorer Actions
- Generic API Actions
- Invoice Actions
- Mediation Actions
- Order Actions
- Quote Actions
- Subscription Actions
Overview
The File Explorer - Download File operation in this custom n8n node allows you to download a file from the Opencell server by specifying its path. This is useful for automating workflows that require retrieving files stored on the Opencell backend, such as reports, logs, or exported data.
Common scenarios:
- Automatically fetching generated invoices, reports, or export files for further processing.
- Integrating Opencell file storage with other systems (e.g., sending downloaded files via email or uploading them to cloud storage).
- Scheduled backups or archiving of files from Opencell.
Practical example:
You could use this node to download a daily report file and then process it in subsequent workflow steps, such as parsing its contents or forwarding it to another service.
Properties
| Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects the authentication method for connecting to Opencell ("Basic Authentication" or "OAuth2"). |
| Body Content Type | hidden | Internal property; always set to "multipart-form-data". Not user-configurable. |
| File Path | string | The full path to the file you want to download from the Opencell server. Required. |
Output
- The output will be a JSON object containing the result of the file download operation.
- If the file is successfully downloaded, the response will typically include metadata about the file or the file content itself, depending on how the API returns the data.
- Binary Data: If the API returns binary file content, the node may output binary data. In this case, the binary field will contain the actual file data, which can be used in downstream nodes (e.g., Write Binary File, Email Attachment).
Dependencies
- External Service: Requires access to an Opencell instance with the REST API enabled.
- Authentication: You must configure either Basic Authentication or OAuth2 credentials in n8n for the Opencell API.
- n8n Configuration: Ensure the relevant credentials are set up in your n8n instance under the name
opencellApi(for Basic Auth) oropencellOAuth2Api(for OAuth2).
Troubleshooting
Common issues:
- Invalid Credentials: If authentication fails, you may see errors like
Username/password error. Error code : 401. Double-check your credentials and authentication method. - File Not Found: If the specified file path does not exist, the API may return a 404 error or a message indicating the file was not found. Verify the file path is correct.
- Permission Denied: If your Opencell user does not have permission to access the requested file, you may receive a 403 error.
- Network/Connection Issues: Errors related to connectivity (timeouts, DNS errors) indicate network problems between n8n and the Opencell server.
How to resolve:
- Check and update your credentials in n8n.
- Confirm the file path exists and is accessible.
- Ensure your user account has the necessary permissions.
- Test connectivity to the Opencell API endpoint from your n8n host.