Lark Base

Lark Base Management

Actions21

Overview

The "Update Records" operation for the "Record" resource in this node allows users to update one or multiple records within a specified table of a bitable app in Lark Suite. This is useful when you want to programmatically modify existing data entries, such as updating task statuses, changing assigned personnel, or adjusting deadlines.

Common scenarios include:

Automating updates to project management tables when tasks progress.
Syncing external data sources with your bitable records.
Bulk updating multiple records based on certain triggers or workflows.

For example, you could update the "status" field of several records to "completed" after a workflow finishes, or change the "performer" field to assign new team members.

Properties

Name	Meaning
Authentication	Method used to authenticate API requests. Options: Tenant Token, OAuth2.
App Token	The unique identifier (app_token) of the bitable app where the records reside. Required to specify which app's data to update.
Table Id	The identifier of the specific table within the bitable app containing the records to update.
Records	A collection of record items to update. Each item contains JSON defining the fields and their new values. Multiple records can be updated in one request.
Custom Body	An optional custom JSON body to send instead of the standard structured input. Allows advanced users to fully customize the update payload sent to the API.
Use Custom Body	Boolean flag indicating whether to use the Custom Body property instead of the structured Records input.

Details on Records property structure

Each record item should be a JSON object with at least:

record_id (string): The ID of the record to update.
fields (object): Key-value pairs representing the fields to update and their new values. Values can be strings, numbers, booleans, arrays, or nested objects depending on the field type.

Example snippet for a single record update:

{
  "record_id": "rec123",
  "fields": {
    "status": "completed",
    "performer": [{"id": "user456"}],
    "deadline": 1680000000
  }
}

Output

The node outputs JSON data representing the response from the Lark Suite API after attempting to update the records. This typically includes confirmation of the updated records, their IDs, and any metadata returned by the API.

If the API supports it, the output may also contain error messages or status codes indicating success or failure per record.

No binary data output is expected from this operation.

Dependencies

Requires an active connection to Lark Suite's Open APIs.
User must provide either a Tenant Token or OAuth2 authentication credential.
Requires valid app_token and table_id identifying the target bitable app and table.
Network access to https://open.larksuite.com/open-apis is necessary.

Troubleshooting

Invalid App Token or Table Id: If these identifiers are incorrect or missing, the API will reject the request. Verify that the app token and table id correspond exactly to your bitable app and table.
Authentication Errors: Using expired or invalid tokens will cause authentication failures. Ensure your credentials are up to date and have sufficient permissions.
Malformed Records JSON: Incorrectly formatted JSON in the Records or Custom Body properties can cause request failures. Validate JSON syntax and ensure required fields like record_id and fields are present.
API Rate Limits: Excessive requests may trigger rate limiting. Implement retries with backoff if needed.
Use Custom Body Flag: If enabled but the custom body is malformed or incomplete, the request may fail. Double-check the custom JSON structure.