Feishu Node

Overview

This node integrates with a cloud storage or collaboration platform (referred to as "云空间" or "Cloud Space") to upload files or media assets. It supports uploading various types of content such as document images, spreadsheet images, document files, and other specialized file categories. This functionality is useful for automating the process of adding files to specific locations within the cloud environment, enabling workflows that require dynamic file management, backup, or sharing.

Practical examples include:

• Automatically uploading screenshots or images generated during a workflow to a designated document folder.
• Uploading exported reports or spreadsheets directly into the cloud space for team access.
• Managing virtual backgrounds or multimedia assets by programmatically placing them in the correct repository.

Properties

Name	Meaning
上传点的类型	The type/category of the upload target. Options include: - 旧版文档图片 (Old Document Image) - 新版文档图片 (New Document Image) - 电子表格图片 (Spreadsheet Image) - 旧版文档文件 (Old Document File) - 新版文档文件 (New Document File) - 电子表格文件 (Spreadsheet File) - Vc 虚拟背景（灰度中，暂未开放）(Virtual Background, currently in grayscale testing) - 多维表格图片 (Multi-dimensional Table Image) - 多维表格文件 (Multi-dimensional Table File) - 同事圈（灰度中，暂未开放）(Colleague Circle, currently in grayscale testing) - 云文档导入文件 (Cloud Document Import File)
上传点的 Token	A token string identifying the specific upload point or node within the cloud space where the file will be uploaded. This acts as an authorization or location identifier.
二进制文件字段	The name of the binary data field from the input item that contains the file to be uploaded. Default is "file".
文件名称	Optional custom name for the file being uploaded. If not provided, the original file name may be used.

Output

The node outputs JSON data representing the result of the upload operation for each input item processed. Each output item corresponds to one upload attempt and includes metadata about the uploaded file or any error information if the upload failed.

If the node handles binary data, it uses the specified binary field to read the file content for upload. The output does not explicitly provide binary data but rather the response or status after uploading.

Dependencies

• Requires an API key credential for authenticating with the cloud platform's API.
• The node depends on the platform's API endpoints corresponding to the selected resource and operation.
• Proper configuration of the upload token and permissions is necessary to allow file uploads.
• The node uses n8n's internal helper methods for handling binary data and constructing execution metadata.

Troubleshooting

• Common issues:

  • Incorrect or expired upload token leading to authorization failures.
  • Missing or incorrectly named binary file field causing the node to fail reading the file.
  • Unsupported file types or sizes rejected by the cloud platform.
  • Network or API errors during upload.

• Error messages:

  • Errors indicating "未实现方法" (method not implemented) suggest the selected resource-operation combination is not supported.
  • API errors returned from the cloud service typically include error messages; these should be checked for permission or quota issues.
  • If the node throws a generic execution error, verify that the binary data exists and the upload token is valid.

• Resolutions:

  • Double-check the upload token and ensure it has proper permissions.
  • Confirm the binary field name matches the actual input data.
  • Validate file size and format against platform limits.
  • Enable "Continue On Fail" to handle partial failures gracefully.

Links and References

• Refer to the cloud platform's official API documentation for details on upload points and tokens.
• n8n documentation on handling binary data and custom node development.
• General best practices for file uploads and API authentication.