Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node interacts with the Feishu platform to perform various operations on different resources. Specifically, for the "云文档" (Cloud Document) resource and the "获取文档基本信息" (Get Document Basic Information) operation, it retrieves fundamental details about a specified document by its unique identifier. This is useful when you need to fetch metadata or summary information about a document stored in Feishu without downloading the entire content.

Practical examples include:

  • Automatically retrieving document titles, authors, or last modified dates to display in dashboards.
  • Validating document existence or status before performing further automated workflows.
  • Integrating document metadata into reporting or notification systems.

Properties

Name Meaning
文档 ID The unique identifier of the document.

Output

The node outputs JSON data containing the basic information of the specified document. The exact structure depends on the Feishu API response but typically includes fields such as document title, creator, creation date, last modified date, and possibly document status or permissions.

If the node supports binary data output (not indicated here), it would represent document content or attachments; however, for this operation, only JSON metadata is expected.

Dependencies

  • Requires an API key credential for authenticating with the Feishu platform.
  • Needs network access to Feishu's API endpoints.
  • The node depends on internal helper functions and a resource-operation factory to map the requested operation to the correct API call.

Troubleshooting

  • Common issues:

    • Invalid or missing document ID will cause the API call to fail.
    • Authentication errors if the API key credential is incorrect or expired.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • "未实现方法: doc.doc:getInfo" indicates that the requested resource-operation combination is not implemented; ensure the correct resource and operation names are used.
    • API errors returned from Feishu will be propagated; check the error message for details like permission denied or document not found.

  • Resolutions:

    • Verify the document ID is correct and exists in Feishu.
    • Confirm the API credentials are valid and have sufficient permissions.
    • Check network connectivity and proxy settings if applicable.
    • Use the node’s “Continue On Fail” option to handle errors gracefully in workflows.

Links and References

Discussion