Overview
This node allows users to delete rows from a specified table within a project (or base) in the Lake platform. It supports multiple API versions and authentication methods, enabling flexible integration with different Lake setups. The node is useful for automating data cleanup, removing obsolete or incorrect records, or managing data lifecycle programmatically.
Typical use cases include:
- Automatically deleting rows based on certain conditions or triggers.
- Integrating with other workflows that require row removal after processing.
- Managing data consistency by removing duplicates or outdated entries.
For example, you might use this node to delete user records from a customer database when they unsubscribe or to remove temporary data after a batch process completes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: "API Token" or "User Token". |
| API Version | Select the API version 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 where the base/project resides. |
| Base Name or ID | (Only for API version v0.200.0 Onwards) Select or specify the base (project) containing the table. |
| Project ID | (For API versions before v0.200.0) Specify the project ID containing the table. |
| Project Name or ID | (For API version v0.90.0 Onwards) Select or specify the project/base containing the table. |
| Table Name or ID | Select or specify the table from which to delete rows. |
| Table | (For API version before v0.90.0) Specify the table name. |
| Primary Key Type | Defines the primary key field type used to identify rows to delete. Options are: - Default ( id): standard primary key.- Imported From Airtable ( ncRecordId).- Custom: specify a custom primary key field name. |
| Field Name | (Shown if Primary Key Type is Custom) Specify the custom primary key field name. |
| Row ID Value | The value of the primary key field identifying the row to delete. Required for each item. |
Output
The node outputs an array of JSON objects corresponding to each input item processed:
- For API version 1 (before v0.90.0), it returns the original input items as output upon successful deletion.
- For API version 2 (v0.90.0 onwards), it returns an array indicating success or failure per row. If a row could not be deleted (e.g., does not exist), an error message is returned for that item.
- For API version 3 (v0.200.0 onwards), it returns the raw response from the API for each deletion request.
The output json field contains either confirmation of deletion or error details if deletion failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token or user token credential configured in n8n.
- Depends on the Lake platform's REST API endpoints, which vary by selected API version.
- Uses internal helper functions to make HTTP requests and handle pagination or bulk operations.
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 Errors: Ensure the provided API token or user token has sufficient permissions to delete rows in the specified project/base/table.
- Incorrect API Version: Using the wrong API version setting may cause endpoint mismatches or unexpected errors. Confirm the Lake instance version and select the matching API version.
- Missing Required Parameters: The node requires project/base ID, table name/ID, and row ID values. Missing or incorrect values will cause failures.
- Continue On Fail Behavior: If enabled, the node will continue processing remaining items even if some deletions fail, returning error messages per failed item.
Links and References
- Lake API Documentation (generic reference; adjust based on actual Lake API docs)
- n8n Expressions Documentation
- n8n Node Development Guide