Lark Files icon

Lark Files

Lark Files Management

Actions28

Overview

The node provides functionality to manage comments and replies within documents in the Lark Files system. Specifically, the "Delete A Reply" operation under the "Comment" resource allows users to delete a specific reply to a comment on a document. This is useful for scenarios where a user needs to moderate or clean up discussions by removing outdated or inappropriate replies.

Practical examples include:

  • Removing a mistaken or irrelevant reply from a collaborative document.
  • Moderating comments in shared files to maintain clarity.
  • Automating cleanup of comment threads via workflows.

Properties

Name Meaning
Authentication Method of authentication to use: either "Tenant Token" or "OAuth2".
File Type Type of the document (optional). Used as a query parameter in the request.
File Token Token identifier of the document where the comment exists. Required to specify the target file.
Comment Id Numeric ID of the comment containing the reply to be deleted.
Reply Id Numeric ID of the reply that should be deleted.
Options Additional options; currently supports "Use Custom Body" boolean flag to send a custom request body if needed.

Output

The output of this operation is the JSON response returned by the Lark Files API after attempting to delete the specified reply. Typically, this will contain status information indicating success or failure of the deletion request.

No binary data is output by this node.

Dependencies

  • Requires an active connection to the Lark Suite Open APIs.
  • Needs either a Tenant Token credential or OAuth2 credential configured in n8n for authentication.
  • The base URL for API requests is https://open.larksuite.com/open-apis.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication tokens can cause authorization failures.
    • Incorrect or missing file_token, comment_id, or reply_id will result in errors indicating resource not found or invalid parameters.
    • Using an unsupported file_type may lead to unexpected API behavior.

  • Error messages:

    • Authorization errors typically indicate problems with the provided credentials; ensure tokens are valid and have necessary permissions.
    • "Not Found" errors suggest the specified comment or reply IDs do not exist or do not belong to the given file token.
    • API rate limits or network issues may cause request failures; retrying after some time or checking network connectivity can help.

Links and References

Discussion