Lark Base icon

Lark Base

Lark Base Management

Actions21

Overview

The node provides functionality to batch delete tables within a specified app in the Lark Suite Docs Bitable service. This operation is useful when you need to remove multiple tables at once from a bitable app, streamlining management and cleanup tasks.

Common scenarios include:

  • Automating the removal of obsolete or temporary tables in bulk.
  • Managing large datasets where manual deletion would be inefficient.
  • Integrating with workflows that require dynamic table lifecycle management.

For example, if you have an app containing several project tracking tables that are no longer needed, this node can delete all those tables in one request by specifying their IDs.

Properties

Name Meaning
Authentication Method of authentication to use: either "Tenant Token" or "OAuth2".
App Token The token identifying the bitable app from which tables will be deleted.
Table Ids A collection of table IDs to delete. You can add multiple table IDs here for batch deletion.
Use Custom Body Boolean option to specify whether to send a custom JSON body instead of the standard format.
Custom Body When "Use Custom Body" is enabled, allows providing a fully custom JSON payload for the request.

Output

The node outputs JSON data representing the response from the batch delete API call. This typically includes information about the success or failure of the deletion operation for each specified table ID.

No binary data output is involved.

Dependencies

  • Requires access to the Lark Suite Docs Bitable API.
  • Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
  • Requires the bitable app token to identify the target app.
  • The base URL for API requests is https://open.larksuite.com/open-apis.

Troubleshooting

  • Invalid App Token: If the app token is incorrect or missing, the API will reject the request. Ensure the token matches the target bitable app.
  • Invalid Table IDs: Providing non-existent or malformed table IDs will cause errors or partial failures. Verify table IDs before submission.
  • Authentication Errors: Using wrong or expired credentials will result in authorization failures. Refresh tokens or verify credential setup.
  • Custom Body Format Issues: When using a custom JSON body, ensure it matches the expected API schema to avoid request rejections.
  • Network or API Limits: Large batches might hit rate limits or timeouts; consider splitting into smaller batches if issues arise.

Links and References

Discussion