Larkbase icon

Larkbase

Truy vấn dữ liệu từ Larkbase API - Larksuite Base
Join our community

Actions3

Overview

This node interacts with the Larkbase API to perform operations on records within a specified table. Specifically, the 'Update Records' operation allows users to update multiple records in bulk by providing a JSON array of records, each containing a record ID and fields to update. This is useful for scenarios where batch updates to a database or spreadsheet-like table are needed, such as updating product information, status changes, or notes across many entries at once.

Use Case Examples

  1. Updating product details like name and price for multiple products in a sales database.
  2. Changing the status and adding notes to several records in a project management table.

Properties

Name Meaning
Base ID / App Token Identifier for the base or application token used to access the Larkbase API.
Access Token Authentication token required to authorize API requests.
Table ID Identifier of the table where records will be updated.
Records JSON JSON array of records to update, each must include a 'record_id' and the fields to update.
Bỏ qua Records không hợp lệ Boolean flag to skip invalid records that do not have a 'record_id' instead of stopping with an error.
Kích thước Chunk Maximum number of records to send in a single API call, up to 500.
Debug Level Level of debug information returned: Basic (no sensitive data), Standard (moderate detail), or Detailed (full request/response data).

Output

JSON

  • records - Array of updated record objects returned from the API.
  • status - Status of the update operation, typically 'success'.
  • recordCount - Number of records successfully updated.
  • skippedRecords - Number of records skipped due to invalid data (if skipping enabled).
  • debug - Debug information based on the selected debug level.

Dependencies

  • Requires access to Larkbase API with valid App Token and Access Token credentials.

Troubleshooting

  • Common issues include missing or invalid App Token, Access Token, or Table ID, which will cause errors before API calls.
  • Invalid JSON syntax in the 'Records JSON' input will cause parsing errors; ensure the JSON is well-formed.
  • If 'skipInvalidRecords' is false, any record missing 'record_id' will cause the operation to fail; enabling skip can avoid this.
  • Warnings are logged if tokens do not follow expected formats, which may indicate misconfiguration.

Links

Discussion