Feishu Node

Overview

This node provides integration with a cloud document service, specifically enabling the deletion of blocks within documents. The "删除块" (Delete Block) operation allows users to remove a specific block from a document by specifying the document ID and the block ID. This is useful in scenarios where parts of a document need to be programmatically removed or cleaned up, such as automating content management workflows, removing outdated sections, or managing collaborative document edits.

Practical examples include:

• Automatically deleting comment blocks or annotations after review.
• Removing obsolete content blocks during document version updates.
• Cleaning up temporary or draft sections before finalizing a document.

Properties

Name	Meaning
文档 ID	The unique identifier of the document from which a block will be deleted.
父块 ID	The unique identifier of the parent block that is to be deleted.
文档版本	The version number of the document to query. A value of -1 indicates the latest version of the document.
操作的唯一标识	A unique identifier for the operation, used for idempotency. If empty, a new request is initiated; if provided, it ensures the update operation is idempotent by matching this token with the API's client_token response.

Output

The node outputs JSON data representing the result of the delete block operation. This typically includes confirmation of the deletion and any metadata returned by the API related to the operation status. The output does not explicitly handle binary data.

Dependencies

• Requires an API key credential for authenticating with the cloud document service.
• The node depends on the external cloud document API to perform block deletion.
• Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

• Common Issues:

  • Invalid or missing document ID or block ID will cause the operation to fail.
  • Using an incorrect document version may lead to conflicts or failure to find the block.
  • Reusing the same operation unique identifier incorrectly might cause unexpected idempotency behavior.

• Error Messages:

  • Errors indicating "未实现方法" (method not implemented) suggest the requested resource-operation combination is unsupported.
  • API errors related to authentication failures indicate issues with the provided API key or credentials.
  • Network or timeout errors may occur if the external service is unreachable.

• Resolutions:

  • Verify all required properties are correctly set and valid.
  • Ensure the API credentials are properly configured and have sufficient permissions.
  • Use unique operation tokens for each distinct delete request unless intentionally retrying the same operation.

Links and References

• Refer to the official cloud document service API documentation for detailed information on block deletion endpoints and parameters.
• Consult n8n documentation on how to configure API credentials and handle node errors.