Lark Base icon

Lark Base

Lark Base Management

Overview

This node is designed to delete a specific record from a table within a Lark Suite Bitable app. It is useful in scenarios where you need to programmatically remove outdated, incorrect, or unnecessary data entries from your collaborative tables hosted on Lark Suite. For example, automating the cleanup of records after processing them or removing test data during development.

Properties

Name Meaning
Authentication Method used for authenticating API requests. Options: Tenant Token, OAuth2
App Token The unique identifier (token) of the Bitable app containing the target table
Table Id Identifier of the table within the Bitable app from which the record will be deleted
Record Id Identifier of the specific record to delete
Options Additional optional settings; currently supports "Use Custom Body" (boolean) to override request body

Output

The node outputs JSON data representing the response from the Lark Suite API after attempting to delete the record. Typically, this includes status information indicating whether the deletion was successful. There is no binary output.

Dependencies

  • Requires access to Lark Suite Open APIs.
  • Needs either a Tenant Token or OAuth2 authentication configured in n8n credentials.
  • Requires the base URL https://open.larksuite.com/open-apis for API requests.
  • The user must provide valid App Token, Table Id, and Record Id values corresponding to their Lark Suite Bitable setup.

Troubleshooting

  • Invalid App Token, Table Id, or Record Id: Ensure these identifiers are correct and correspond to existing resources in your Lark Suite Bitable app.
  • Authentication errors: Verify that the selected authentication method is properly configured with valid credentials.
  • Permission issues: The token used must have sufficient permissions to delete records in the specified app and table.
  • API rate limits or network errors: Check connectivity and API usage limits imposed by Lark Suite.
  • If using the "Use Custom Body" option, ensure the custom body format matches API expectations to avoid request failures.

Links and References

Discussion