Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node interacts with a knowledge base service to retrieve a list of knowledge spaces (wiki spaces). It is useful for scenarios where users want to programmatically access and manage collections of documents or knowledge repositories within an organization. For example, it can be used to fetch available knowledge spaces for display in a custom dashboard, synchronize knowledge space metadata with other systems, or automate documentation workflows.

Properties

Name Meaning
每页大小 Page size for pagination, maximum value is 50. Controls how many knowledge spaces are returned per request.
分页标记 Pagination token used to fetch the next page of results. Leave empty on the first request.
语言 Language code for displaying the names of the knowledge spaces. Options include: 简体中文, 印尼语, 德语, 英语, 西班牙语, 法语, 意大利语, 葡萄牙语, 越南语, 俄语, 印地语, 泰语, 韩语, 日语, 繁体中文（中国香港）, 繁体中文（中国台湾）. Default is 简体中文 (zh).

Output

The node outputs JSON data representing the list of knowledge spaces retrieved from the service. Each item in the output array corresponds to a knowledge space with its associated metadata such as name, ID, and possibly other descriptive fields depending on the API response. The output does not include binary data.

Dependencies

  • Requires an API key credential for authentication with the external knowledge base service.
  • The node depends on the underlying API client implemented in the bundled resource factory to make requests.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Providing an invalid pagination token may result in errors or empty responses.
    • Requesting a page size larger than 50 may be rejected by the API.
  • Error messages:
    • Errors related to "未实现方法" (unimplemented method) indicate that the requested resource-operation combination is not supported.
    • Network or API errors will be logged and can be handled by enabling "Continue On Fail" to skip problematic items.
  • To resolve errors, verify API credentials, ensure correct parameter values, and check network connectivity.

Links and References

Discussion