Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node integrates with the "多维表格" (Multidimensional Table) service to update a specific record in a data table. It is useful when you need to programmatically modify existing records within a multidimensional table, such as updating user information, status, or any other data fields stored in the table.

Typical use cases include:

  • Automating updates to records based on external triggers or workflows.
  • Synchronizing data between different systems by updating records in the table.
  • Correcting or enriching data entries without manual intervention.

For example, you might use this node to update a user's profile information in a multidimensional table after receiving new data from another system.

Properties

Name Meaning
多维表格 Token The unique identifier token for the multidimensional table App.
多维表格 ID The unique identifier of the multidimensional table where the record resides.
记录 ID The unique identifier of the record to update within the table. Obtained via a record query API.
用户 ID 类型 The type of user ID used; options are: Open ID, Union ID, User ID.
是否忽略一致性读写检查 Boolean flag indicating whether to ignore consistency read-write checks during the update.
请求体JSON JSON object representing the request body, specifically the fields to update in the record.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON contains the response from the update operation on the multidimensional table record. This typically includes confirmation of the updated fields and metadata about the record.

If the node supports binary data output, it would represent associated file attachments or media linked to the record, but this is not indicated in the provided code or properties.

Dependencies

  • Requires an API key credential for authenticating with the multidimensional table service.
  • The node depends on the multidimensional table's REST API endpoint for updating records.
  • Proper configuration of the API token and table identifiers is necessary.
  • The node uses internal helper methods from the n8n workflow environment for execution and error handling.

Troubleshooting

  • Common Issues:

    • Invalid or expired API token leading to authentication failures.
    • Incorrect table ID or record ID causing "record not found" errors.
    • Malformed JSON in the request body resulting in validation errors.
    • Permission issues if the API token lacks rights to update records.

  • Error Messages:

    • Errors thrown by the node will include messages from the underlying API or internal validation.
    • If the node encounters an unimplemented operation, it throws an error indicating the missing method.
    • When continueOnFail is enabled, errors for individual items are captured in the output rather than stopping execution.

  • Resolutions:

    • Verify that the API token is valid and has sufficient permissions.
    • Double-check the table and record IDs for correctness.
    • Ensure the JSON request body follows the API specification.
    • Use the node’s debug logs to trace the exact failure point.

Links and References

Discussion