Overview
This node allows you to delete rows from a specified table in a database managed by the Lake platform. It supports multiple API versions and authentication methods, enabling flexible integration with different Lake setups.
Common scenarios where this node is useful include:
- Automating data cleanup by removing obsolete or incorrect records.
- Integrating with workflows that require conditional deletion of database entries.
- Managing data lifecycle by programmatically deleting rows based on external triggers.
For example, you could use this node to delete user records that have been marked as inactive in an external system or remove temporary data after processing.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: either "API Token" or "User Token". |
| API Version | Select the version of the Lake API to use: "Before v0.90.0", "v0.90.0 Onwards", or "v0.200.0 Onwards". This affects endpoint URLs and request formats. |
| Workspace Name or ID | (Only for API version v0.200.0 Onwards) Select or specify the workspace containing the base. |
| Base Name or ID | (Only for API version v0.200.0 Onwards) Select or specify the base (project) within the workspace. |
| Project ID | (For API versions Before v0.90.0 and v0.90.0 Onwards) Specify the project ID or select from the list. |
| Table Name or ID | The target table from which to delete rows. You can choose from a list or specify an ID. |
| Primary Key Type | Defines the type of primary key used to identify rows: "Default" (id), "Imported From Airtable" (ncRecordId), or "Custom" (specify a custom field name). Only relevant for API versions Before v0.200.0 and operations delete/update. |
| Field Name | When using a custom primary key type, specify the exact field name here. |
| Row ID Value | The value of the primary key identifying the row to delete. Required for each item processed. |
Output
The output is a JSON array representing the result of the delete operation for each input item:
- For API version Before v0.90.0, the output simply returns the original input items unchanged.
- For API version v0.90.0 Onwards, the output contains success indicators or error messages per item. If a row could not be deleted (e.g., it does not exist), an error message is returned unless the node is set to continue on failure.
- For API version v0.200.0 Onwards, the output reflects the response from the API directly, typically indicating success or failure per deleted record.
No binary data output is produced by this operation.
Dependencies
- Requires valid authentication credentials: either an API token or a user token configured in n8n.
- Depends on the Lake API endpoints, which vary by selected API version.
- Uses dynamic loading of workspaces, bases/projects, and tables via API calls to populate dropdowns.
- Requires network access to the Lake API service.
Troubleshooting
- Row Not Found Error: If the node reports that a row with the specified ID could not be deleted, verify that the ID exists in the target table and that the correct primary key type and field name are selected.
- Authentication Failures: Ensure that the provided API token or user token has sufficient permissions to delete rows.
- Incorrect API Version: Using the wrong API version setting may cause endpoint errors. Confirm the Lake instance version and select the matching API version.
- Missing Required Parameters: The node requires the project/base ID, table ID, and row ID values. Missing or incorrect values will cause errors.
- Continue on Fail Behavior: If enabled, the node will continue processing other items even if some deletions fail, returning error details in the output.
Links and References
- Lake API Documentation (general reference for API endpoints)
- n8n Expressions Documentation (for dynamic parameter expressions)
- NocoDB Integration Guide (related since Lake is based on NocoDB concepts)