Lark Base icon

Lark Base

Lark Base Management

Actions21

Overview

The "Create A Record" operation in the "Record" resource allows users to add new records into a specified table within a bitable app on the Lark platform. This node is useful for automating data entry tasks, integrating external data sources, or dynamically populating tables based on workflow events.

Typical use cases include:

  • Automatically logging form submissions into a bitable.
  • Syncing data from other applications into a Lark bitable.
  • Creating records as part of a larger automated process involving Lark services.

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 record will be created
Table Id The identifier of the specific table within the bitable app where the record will be added
Records Collection of one or more records to create. Each record contains a JSON object representing its fields
Custom Body Optional raw JSON body to send instead of using the structured properties. Allows full control over payload
Options > Use Custom Body Boolean flag to toggle between using the structured "Records" property or sending a custom JSON body

Details on complex properties:

  • Records: This is a fixed collection allowing multiple entries. Each entry must have a fields JSON object defining the key-value pairs for the record's columns.

  • Custom Body: When enabled, this JSON input overrides the standard "Records" property and sends the provided JSON directly in the request body. Useful for advanced scenarios or when the user wants to customize the payload beyond the UI capabilities.

Output

The node outputs the response from the Lark API after creating the record(s). The main output field is json, which contains the API response data. This typically includes details about the newly created record(s), such as their IDs and stored field values.

If binary data were involved (not indicated here), it would be summarized accordingly, but this node deals with JSON data only.

Dependencies

  • Requires an active connection to Lark's Open APIs.
  • Needs either a Tenant Token or OAuth2 authentication credential configured in n8n.
  • Requires valid app_token and table_id identifiers corresponding to the target bitable app and table.
  • Network access to https://open.larksuite.com/open-apis is necessary.

Troubleshooting

  • Invalid App Token or Table ID: Ensure that the app_token and table_id are correct and correspond to existing resources in your Lark bitable app.
  • Authentication Errors: Verify that the selected authentication method is properly configured and the credentials are valid.
  • Malformed Records JSON: When using the "Records" property, ensure each record's fields JSON is well-formed and matches the expected schema of the bitable table.
  • Custom Body Usage: If enabling "Use Custom Body", make sure the JSON structure matches the API requirements exactly; otherwise, the request may fail.
  • API Rate Limits or Permissions: Check that the API credentials have sufficient permissions and that you are not exceeding rate limits imposed by Lark.

Links and References

Discussion