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 - Upload Zipped File operation in this n8n node allows users to upload a zipped file (provided as a base64-encoded string) to a specified path on the Opencell server. This is useful for automating the transfer of compressed files, such as backups, data packages, or configuration bundles, directly into the Opencell file system via workflow automation.
Common scenarios:
- Automating deployment of zipped resources to Opencell.
- Uploading large datasets or multiple files in a single compressed archive.
- Integrating external systems that generate zipped files with Opencell's file storage.
Example:
A workflow receives a zipped report from another system, encodes it in base64, and uploads it to a specific directory in Opencell for further processing.
Properties
| Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects the authentication method for connecting to Opencell (Basic Authentication or OAuth2). |
| Body Content Type | hidden | Always set to "multipart-form-data" (not user-configurable for this operation). |
| File Content | string | The base64-encoded content of the zipped file to be uploaded. Required. |
| File Path | string | The destination path (including filename) where the zipped file will be stored. Required. |
Output
- The output is a JSON object containing the response from the Opencell API after uploading the zipped file.
- The structure of the output depends on the Opencell API's response for the
/opencell/api/rest/admin/files/uploadZippedFileBase64endpoint. - Typically, it may include status information, file metadata, or error messages if the upload fails.
Example output:
{
"status": "success",
"message": "File uploaded successfully",
"filePath": "/desired/path/filename.zip"
}
Note: Actual fields depend on Opencell's API response.
Dependencies
- External Service: Requires access to an Opencell instance with the REST API enabled.
- Authentication: Needs valid credentials for either Basic Authentication or OAuth2, configured in n8n credentials.
- Environment: The Opencell API URL and credentials must be set up in n8n.
Troubleshooting
Common issues:
- Invalid Base64 Content: If
File Contentis not properly base64-encoded, the upload will fail. - Incorrect File Path: If the specified
File Pathdoes not exist or is invalid, the API may return an error. - Authentication Errors: Invalid or missing credentials will result in authentication failures.
- API Connectivity: Network issues or incorrect API URLs can prevent successful uploads.
Error messages and resolutions:
"Invalid credentials (unknown error)": Check your authentication settings in n8n."Host error. Error code : <code>": Verify the Opencell API URL and network connectivity."File upload failed"or similar: Ensure the file content is correctly encoded and the file path is valid.