Lark Base icon

Lark Base

Get data from Lark Base
Join our community

Actions2

Overview

The "Create Many" operation of the Lark Base node allows users to create multiple records (up to 500 at a time) in a specified table within a Lark Base application. This is useful for batch inserting data into a database-like structure managed by Lark Base, which can be beneficial when migrating data, syncing external datasets, or automating bulk data entry.

Practical examples include:

  • Importing a list of contacts or inventory items into a Lark Base table.
  • Automating the creation of multiple task entries from an external project management tool.
  • Syncing data collected from forms or other sources into Lark Base for further processing.

Properties

Name Meaning
App Token The app_token of the Lark Base application where records will be created.
Table ID The identifier of the specific table within the Lark Base app where records will be added.
Records JSON array of record objects to create, with a maximum of 500 records per request.
User ID Type Specifies the category of user ID used in the operation. Options: Open ID, Union ID, User ID.
Client Token A unique identifier (UUIDv4) for the operation to ensure idempotency (avoid duplicate requests).
Ignore Consistency Check Boolean flag indicating whether to bypass consistency checks during read/write operations.

Output

The output JSON contains the response from the Lark Base API after attempting to create the batch of records. Typically, this includes details about the created records such as their IDs and any metadata returned by the API.

If the node supports binary data output, it is not relevant for this operation since it deals with JSON record creation.

Dependencies

  • Requires an API key credential for authenticating with the Lark Base API.
  • The node internally obtains a tenant access token by making a POST request to Lark's authentication endpoint using the provided API credentials.
  • Network access to https://open.larksuite.com/open-apis is required.
  • No additional environment variables are explicitly needed beyond the configured API credentials.

Troubleshooting

  • Failed to get tenant access token: This error occurs if the API credentials are invalid or the authentication request fails. Verify that the API key and secret are correct and have sufficient permissions.
  • API rate limits or quota exceeded: Creating many records at once may hit API limits. Consider splitting large batches or adding delays.
  • Invalid records format: Ensure the JSON array of records conforms to the expected schema by Lark Base; malformed records will cause errors.
  • Idempotency issues: If duplicate records are created, use the Client Token property to make the operation idempotent.
  • Ignoring consistency check: Setting this option to true may lead to faster writes but risks data inconsistency; use with caution.

Links and References

Discussion