Actions28
- File Actions
- Multipart Upload File Actions
- Permission Member Actions
- Comment Actions
- Permissionpublic Actions
- Statistic Actions
- Media Actions
- Multipart Upload Media Actions
- Subscription Actions
- Document Import Actions
Overview
This node facilitates managing files within the Lark platform, specifically focusing on completing multipart file uploads. The "Complete Uploading A File In Blocks" operation finalizes the process of uploading a large file that has been split into multiple blocks. This is useful when dealing with large files that need to be uploaded in chunks to ensure reliability and efficiency.
Typical use cases include:
- Uploading large documents or media files to Lark Docs or Lark Drive.
- Ensuring file integrity by confirming all parts have been uploaded before finalizing.
- Automating file upload workflows where chunked uploads are required due to size constraints or network conditions.
For example, after uploading each block of a video file separately, this node operation would be called to signal the completion of the entire upload, allowing the file to be assembled and made available.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: Tenant Token, OAuth2 |
| Block Num | The number of blocks (chunks) the file was divided into during upload |
| Upload Id | Identifier for the multipart upload session, used to associate blocks with the correct file |
| Custom Body | JSON object to send a custom request body instead of standard parameters |
| Use Custom Body | Boolean flag indicating whether to use the custom JSON body for the request |
Output
The node outputs JSON data representing the response from the Lark API upon completing the multipart upload. This typically includes confirmation details such as success status, file metadata, or error messages if the completion failed.
No binary data output is expected from this operation since it deals with signaling upload completion rather than transferring file content.
Dependencies
- Requires an active authentication credential, either via a Tenant Token or OAuth2 token, configured in n8n.
- Connects to the Lark Suite Open APIs at
https://open.larksuite.com/open-apis. - Proper permissions must be granted to the API credentials to manage file uploads.
Troubleshooting
- Invalid Upload Id: If the provided upload ID does not match any ongoing upload session, the API will return an error. Verify the upload ID is correct and corresponds to the current multipart upload.
- Incorrect Block Number: Providing an incorrect block count may cause the completion to fail. Ensure the block number matches the total number of uploaded blocks.
- Authentication Errors: Using expired or invalid tokens will result in authorization failures. Refresh or reconfigure credentials as needed.
- Network Issues: Connectivity problems can interrupt the request. Retry the operation or check network stability.
- Custom Body Misconfiguration: When using the custom body option, ensure the JSON structure matches the API requirements exactly to avoid malformed request errors.