Definition and Usage
Use this command to update the content of a specific record in a Lark Base table. You can locate the target table either by its name or by its unique ID, then specify the record ID and the new content to write.
Parameter Values
Input Parameters
Parameter Name | Description | Possible Values | Required | Options / Notes |
Lark Base | The connected Lark Base instance to operate on. | A Lark Base object from Connect Lark Base | Yes | Must be created earlier in the workflow using Connect Lark Base. |
Locating mode | How to identify the target table. | By name, By ID | Yes | Choose By name if the table name is stable; choose By ID for reliability across renames. |
Data table name | The name of the table to update. | Any valid table name | Yes (when locating by name) | Only used if Locating mode = By name; spelling and case must match exactly. |
Data table ID | The unique ID of the table to update. | Any valid table ID | Yes (when locating by ID) | Only used if Locating mode = By ID; copy the ID from Lark Base to avoid typos. |
Record ID | The unique ID of the record to update. | Any valid record ID | Yes | Ensure the record exists in the specified table. |
Update content | The new values to write into the record. | Structured update content as required by your table’s fields | Yes | Include only fields you intend to change; make sure field names and value types match the table schema. |
Advanced Settings
No advanced settings available.
Error Handling
Parameter Name | Description |
Throw error & stop | When an error occurs, the action will stop execution. |
Retry command | The action retries the command if an error occurs. |
Ignore error & continue | The action ignores the error and continues workflow execution. |
Variables Produced
This action doesn't produce any variables.
Using Variables in Conditions
You can pass dynamic values from earlier steps into this command. For example, use a variable for the table ID, record ID, or update content that you obtained or constructed earlier in the workflow. If the UI marks a field with {x}, it indicates that the field supports variables. Build your workflow so upstream actions supply these values before this command runs.
Notes
Connect to Lark Base first and keep the connection valid for this step.
Choose a single locating method: provide Data table name only when using By name, or Data table ID only when using By ID.
Verify the Record ID belongs to the specified table; mismatched IDs will cause update failures.
Ensure Update content aligns with the table’s field names and data types; invalid fields or types can cause errors.
Updating an empty or non-existent field may be rejected depending on the table’s schema rules.