Lark Base icon

Lark Base

Lark Base Management

Actions21

Overview

The node facilitates batch creation of tables within a specified app in the Lark Suite environment (specifically for the "Docs Bitable Table" resource). It allows users to create multiple tables at once by specifying their names. This is useful when setting up or managing multiple data tables programmatically, such as initializing a new workspace with predefined tables or automating table creation based on external data.

Practical examples:

  • Automatically creating several project tracking tables in a new app.
  • Bulk setup of inventory or customer data tables in a business application.
  • Migrating or syncing table structures from another system into Lark Suite.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: Tenant Token, OAuth2
App Token The unique token identifying the target app where tables will be created. Must be a valid alphanumeric string.
Tables A collection of table items to create. Each item requires a name property specifying the table's name. Multiple tables can be added.
Custom Body Optional JSON body allowing full customization of the request payload instead of using the standard Tables input. Should follow the structure { "tables": [ { "name": "string" } ] }.
Options > Use Custom Body Boolean flag indicating whether to send the custom JSON body instead of the structured Tables input.

Output

The node outputs JSON data representing the response from the Lark Suite API after attempting to create the tables. This typically includes details about the newly created tables such as their IDs, names, and any metadata returned by the API.

If binary data were involved (not indicated here), it would represent file contents or attachments related to the tables, but this node focuses on JSON responses only.

Dependencies

  • Requires an active connection to Lark Suite APIs.
  • Needs either a Tenant Token or OAuth2 authentication credential configured in n8n.
  • Requires a valid App Token identifying the target app within Lark Suite.
  • Network access to https://open.larksuite.com/open-apis.

Troubleshooting

  • Invalid App Token: If the app token is missing or malformed (non-alphanumeric), the API will reject the request. Ensure the token matches the expected format.
  • Authentication Errors: Using incorrect or expired credentials will cause authorization failures. Verify that the Tenant Token or OAuth2 token is valid and has necessary permissions.
  • Malformed Request Body: When using the custom body option, ensure the JSON is correctly formatted and follows the expected schema (tables array with objects containing name).
  • API Rate Limits or Quotas: Excessive requests may be throttled by Lark Suite. Implement retries or backoff strategies if needed.
  • Empty Table Names: Providing empty or duplicate table names might cause errors or unexpected behavior. Validate inputs before execution.

Links and References

Discussion