Overview
This node allows you to delete rows from a table in the Lake platform, which is a data management system. It supports multiple API versions and authentication methods, enabling flexible integration with different Lake setups.
Typical use cases include:
- Removing obsolete or incorrect data entries from a database table.
- Automating cleanup tasks by deleting rows based on certain criteria.
- Integrating with workflows that require dynamic data removal from Lake tables.
For example, you might use this node to delete user records that have been marked as inactive or to remove temporary data after processing.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: "API Token" or "User Token". This determines how the node authenticates requests to the Lake API. |
| API Version | Select the version of the Lake API to use. Options are: "Before v0.90.0", "v0.90.0 Onwards", and "v0.200.0 Onwards". This affects endpoint URLs and request formats. |
| Workspace Name or ID | (Only for API version 3) Select or specify the workspace where the base (project) resides. |
| Base Name or ID | (API version 2 and 3) Select or specify the base (project) containing the table. Required field. |
| Project ID | (API version 1) Specify the project ID containing the table. Required field. |
| Table Name or ID | (API version 2 and 3) Select or specify the table from which to delete rows. Required field. |
| Table | (API version 1) Specify the name of the table. Required field. |
| Primary Key Type | (API versions 1, 2, and 3) Select the type of primary key used to identify rows: "Default" (id), "Imported From Airtable" (ncRecordId), or "Custom" (specify custom field name). Applies only for delete and update operations. |
| 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 identifying the row to delete. Required field. |
Output
The node outputs an array of JSON objects representing the result of each delete operation:
- For API version 1, it returns the original input items as confirmation.
- For API version 2, it returns an array indicating success or failure per item. If a row could not be deleted (e.g., does not exist), an error message is included.
- For API version 3, it returns the raw response from the API for each deletion.
If the node encounters errors during deletion, it can either stop execution or continue depending on the "Continue On Fail" setting, returning error details in the output.
No binary data is output by this node.
Dependencies
- Requires valid authentication credentials: either an API token or a user token for the Lake API.
- Needs proper configuration of API version and corresponding workspace/base/project/table identifiers.
- Uses internal helper functions to make HTTP requests to the Lake API endpoints.
- Optionally depends on n8n's expression system for dynamic property values.
Troubleshooting
Common issues:
- Incorrect or missing project/base/table IDs will cause failures.
- Using the wrong API version may lead to invalid endpoint URLs or request payloads.
- Specifying a non-existent row ID will result in an error indicating the row could not be found.
- Custom primary key fields must match exactly the field names in the Lake table schema.
Error messages:
"The row with the ID \"<id>\" could not be deleted. It probably doesn't exist."
Means the specified row was not found. Verify the ID and primary key settings.- Network or authentication errors will throw standard API errors; ensure credentials are valid and have sufficient permissions.
- Errors during bulk deletion return individual item errors if "Continue On Fail" is enabled; otherwise, execution stops.
Links and References
- Lake API Documentation (generic reference, replace with actual Lake docs)
- n8n Expressions Documentation
- n8n Node Development Guide
This summary covers the "Delete" operation for the "Row" resource of the Lake node, focusing on static code analysis of the provided source and properties.