Overview
This node integrates with FeiShu Bitable, a collaborative online database service. Specifically, the Record - Update operation allows users to update existing records in a specified Bitable table by providing the record ID and the fields to modify.
Common scenarios where this node is useful include:
- Automating updates to database entries based on external triggers or workflows.
- Synchronizing data changes from other systems into FeiShu Bitable.
- Modifying specific fields of a record without replacing the entire entry.
For example, you might use this node to update a customer’s status or contact information in a Bitable app when a related event occurs elsewhere in your workflow.
Properties
| Name | Meaning |
|---|---|
| App Token | The unique identifier (API token) of the FeiShu Bitable App to access. |
| Table ID | The unique identifier of the target Bitable data table where the record exists. |
| Record ID | The ID of the record to update within the specified table. |
| Fields | A JSON object specifying the fields and their new values to update in the record. Example: {"单行文本": "新的文本内容", "数字": 100}. Must be valid JSON. |
| Additional Fields | Optional extra parameters: • User ID Type: Specifies the type of user ID used (Open ID, User ID, Union ID). • Ignore Consistency Check: Boolean flag to skip consistency checks during read/write operations. |
Output
The node outputs an array of JSON objects representing the updated records. Each output item contains the updated record data as returned by the FeiShu Bitable API.
If binary data were involved, it would typically represent file attachments or media linked to the record, but this operation focuses on JSON field updates only.
Dependencies
- Requires an active FeiShu Bitable API token (App Token) for authentication.
- Needs network access to FeiShu Bitable API endpoints.
- The node depends on internal helper modules for API requests and operations (
./transport/api,./actions/Record/update.operation). - No additional environment variables are explicitly required beyond the API token credential.
Troubleshooting
- Invalid App Token or Table ID: If the provided App Token or Table ID is incorrect or expired, the API will reject the request. Verify credentials and identifiers.
- Malformed JSON in Fields: The
Fieldsproperty must be valid JSON. Syntax errors or invalid field names/types will cause failures. - Record Not Found: Providing a non-existent Record ID will result in an error indicating the record cannot be found.
- Permission Issues: Insufficient permissions for the API token may prevent updating records.
- Consistency Check Errors: If enabled, consistency checks may block updates if conflicts are detected. Use the "Ignore Consistency Check" option cautiously.
- Network or API Errors: Temporary network issues or API downtime can cause request failures; retrying later may help.