Actions26
- Collections Actions
- Records Actions
- Fields Actions
- Chats Actions
- Files Actions
- User Contacts Actions
- Triggers Actions
Overview
The node operation "Complete Upload File" under the "Files" resource is designed to finalize the process of uploading a file to a remote service. After an initial upload session or chunked upload, this operation signals the completion of the upload, making the file available for further use or processing.
This node is beneficial in scenarios where large files are uploaded in multiple parts or when an upload session needs explicit confirmation to complete. For example, after uploading all chunks of a video file to a cloud storage service, this operation would be called to finalize and commit the upload.
Properties
| Name | Meaning |
|---|---|
| Collection Id | The identifier of the collection or folder where the file belongs. |
| File Id | The unique identifier of the file whose upload is being completed. |
Output
The output JSON typically contains information confirming the successful completion of the file upload. This may include metadata about the file such as its final status, identifiers, timestamps, or URLs for accessing the file.
If the node supports binary data output (not explicitly shown here), it would represent the actual file content or related binary attachments.
Dependencies
- Requires an API key credential or similar authentication token to authorize requests.
- Depends on the external service's API endpoint that manages file uploads and collections.
- The base URL for the API must be configured in the node credentials or environment settings.
Troubleshooting
Common Issues:
- Invalid or missing Collection Id or File Id can cause the operation to fail.
- Authentication errors if the API key or token is incorrect or expired.
- Network issues or incorrect base URL configuration can prevent communication with the API.
Error Messages:
- "File not found" — Verify that the File Id is correct and that the file upload was initiated.
- "Collection not found" — Check that the Collection Id exists and is accessible.
- "Unauthorized" — Ensure the API key or authentication token is valid and has necessary permissions.
- "Upload incomplete" — Confirm that all file chunks have been uploaded before calling this operation.
Resolving these errors usually involves verifying input parameters, checking credentials, and ensuring network connectivity.
Links and References
- Refer to the external service's API documentation for detailed information on file upload workflows and required parameters.
- n8n documentation on handling file uploads and managing collections may provide additional context.