Feishu Node

Overview

This node is designed to query a specific record from a multidimensional table (多维表格) by its record ID. It is useful when you need to retrieve detailed information about a single entry within a complex data table, such as fetching user details, transaction records, or any structured data stored in the table.

Practical examples include:

• Retrieving a customer’s profile by their unique record ID.
• Accessing a specific project task's details for further processing.
• Fetching inventory item information based on its record identifier.

Properties

Name	Meaning
多维表格 Token	The unique token identifying the multidimensional table App.
多维表格 ID	The unique identifier of the multidimensional data table.
记录ID	The unique record ID of the entry to be queried in the table.
用户 ID 类型	The type of user ID used; options are: Open ID, Union ID, User ID.
是否返回记录的分享链接	Boolean flag indicating whether to return the shareable link of the record.
是否返回自动计算的字段	Boolean flag indicating whether to include automatically calculated fields in the response.

Output

The output JSON contains the data of the requested record from the multidimensional table. This includes all fields associated with that record, optionally including:

• A shareable URL if requested.
• Automatically calculated fields if enabled.

No binary data output is indicated for this operation.

Dependencies

• Requires an API token credential for authenticating access to the multidimensional table service.
• The node depends on the external multidimensional table API to fetch record data.
• Proper configuration of the API token and table identifiers is necessary.

Troubleshooting

• Common issues:
  • Invalid or expired API token leading to authentication failures.
  • Incorrect table ID or record ID causing "record not found" errors.
  • Insufficient permissions to access the specified record.
• Error messages:
  • Errors related to missing or invalid parameters will prompt validation errors.
  • API errors may be wrapped and surfaced as node execution errors; checking the error message and stack trace can help identify the root cause.
• Resolutions:
  • Verify the correctness and validity of the API token.
  • Confirm the table ID and record ID exist and are accessible.
  • Ensure the user ID type matches the expected format for the API.

Links and References

• Refer to the official documentation of the multidimensional table service for API details.
• Consult n8n community forums for usage examples and troubleshooting tips related to this node.