Actions21
- App Actions
- Table Actions
- View Actions
- Record Actions
- Field Actions
Overview
This node provides functionality to delete a specific table within the "Docs Bitable Table" resource of the Lark Suite platform. It is useful in scenarios where you need to programmatically remove tables from your bitable apps, such as cleaning up unused data structures or automating workspace management.
Practical examples include:
- Automatically deleting temporary or test tables after processing.
- Managing lifecycle of tables in response to external triggers or workflows.
- Integrating with other systems to maintain synchronized data models by removing obsolete tables.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| App Token | The token identifying the bitable app containing the table. Can be selected from a list or provided as an ID string. |
| Table Id | The unique identifier of the table to delete. |
| Options | Additional options for the operation: currently supports "Use Custom Body" (boolean) to specify if a custom request body should be used. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or any error messages returned by the API. There is no binary output.
Dependencies
- Requires valid authentication credentials: either a tenant token or OAuth2 token for Lark Suite API access.
- Needs the bitable app token to identify the app context.
- Relies on the Lark Suite open API endpoint
https://open.larksuite.com/open-apis.
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 Suite environment.
- Authentication Errors: Verify that the chosen authentication method is properly configured and the credentials are valid.
- Permission Issues: The authenticated user or token must have sufficient permissions to delete tables in the specified app.
- API Rate Limits: Be aware of potential rate limits imposed by Lark Suite APIs which might cause failures if exceeded.
- Custom Body Usage: If "Use Custom Body" is enabled but the body is malformed or incomplete, the API call may fail. Double-check the custom payload format.