Actions11
- Table Actions
- Field Actions
- Record Actions
Record → Update a Record
AI-generatedOverview
This node interacts with the LarkBase API to update a specific record in a given table within a specified base. It is useful for scenarios where you need to modify existing data entries in LarkBase, such as updating user information, inventory details, or any other record-based data management. For example, you can update a customer's contact details or change the status of a project task.
Use Case Examples
- Updating a record in a project management table to change the task status from 'In Progress' to 'Completed'.
- Modifying a user's profile information stored in a LarkBase table, such as updating their email address or phone number.
Properties
| Name | Meaning |
|---|---|
| Base ID | The identifier of the LarkBase base where the table resides. Required to specify the base context for the record update. |
| Table ID | The identifier of the table within the base where the record exists. Required to specify which table contains the record to update. |
| Record ID | The identifier of the specific record to update within the table. Required to target the exact record for modification. |
| Record Data | The JSON object containing the fields and their new values to update in the record. Required to specify the data changes to apply. |
Output
JSON
json- The JSON response from the LarkBase API after updating the record, containing details of the updated record or operation status.
Dependencies
- LarkBase API access with valid credentials including app ID and app secret for authentication.
Troubleshooting
- Ensure that the Base ID, Table ID, and Record ID are correctly specified and exist in LarkBase to avoid 'Unknown resource' or 'Unknown operation' errors.
- Verify that the Record Data JSON is correctly formatted and contains valid fields to prevent API errors.
- Check that the API credentials are valid and have the necessary permissions to update records in the specified base and table.
- Common error messages include 'No credentials returned!' indicating missing or invalid credentials, and 'Get tenant_token failed' indicating authentication issues. Resolving these involves verifying credentials and network connectivity.