Actions21
- App Actions
- Table Actions
- View Actions
- Record Actions
- Field Actions
Overview
This node is designed to delete records from a specified table within a LarkSuite Bitable app. It allows users to remove one or multiple records by specifying their identifiers. This operation is useful for managing and cleaning up data stored in LarkSuite Bitable tables, such as removing outdated entries, correcting mistakes, or automating data lifecycle management.
Practical examples include:
- Automatically deleting completed tasks from a project management table.
- Removing user entries that no longer meet certain criteria.
- Cleaning up temporary or test data after processing.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| App Token | The unique token identifying the Bitable app from which records will be deleted. |
| Table Id | Identifier of the specific table within the app where records reside. |
| Records | List of record IDs to delete. Multiple records can be specified here. |
| Custom Body | Optionally provide a custom JSON body for the delete request instead of using the standard format. |
| Options > Use Custom Body | Boolean flag to indicate whether to send a custom request body instead of the default structure. |
Output
The node outputs JSON data representing the response from the LarkSuite API after attempting to delete the specified records. This typically includes status information about the deletion operation, such as success confirmation or error details. There is no binary output.
Dependencies
- Requires an active connection to LarkSuite's open APIs.
- Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
- The base URL for API requests is
https://open.larksuite.com/open-apis. - Proper permissions on the LarkSuite app and table are necessary to perform deletions.
Troubleshooting
- Invalid App Token or Table Id: Ensure the app token and table ID are correct and correspond to existing resources in LarkSuite.
- Authentication Errors: Verify that the selected authentication method is properly configured and the credentials are valid.
- Record Not Found: If specified record IDs do not exist, the API may return errors or partial success; double-check record identifiers.
- Custom Body Misconfiguration: When using a custom body, ensure the JSON structure matches the API requirements to avoid request failures.
- API Rate Limits: Large batch deletions might hit rate limits; consider splitting requests if encountering throttling errors.