Overview
This node integrates with the Lake platform to perform CRUD (Create, Read, Update, Delete) operations on data rows within tables of a project or base. It supports multiple API versions and authentication methods, allowing users to manage their data programmatically inside n8n workflows.
Common scenarios include:
- Automating data entry by creating new rows in a table.
- Retrieving specific rows or bulk fetching many rows for reporting or processing.
- Updating existing rows based on incoming data.
- Deleting rows from a table as part of cleanup or data lifecycle management.
Practical examples:
- Automatically adding new customer records from form submissions.
- Syncing data between Lake tables and other systems by fetching and updating rows.
- Bulk deleting outdated entries based on certain criteria.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: either "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 v0.200.0 onwards) Select or specify the workspace to operate within. |
| 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 or base ID where the table resides. |
| Table Name or ID | Select or specify the table to operate on within the chosen project/base. |
| Resource | Fixed to "Row" for this node, indicating operations are performed on rows within tables. |
| Operation | The action to perform on rows. Options include: Create, Delete, Get (retrieve one), Get Many (retrieve multiple), and Update. |
| Data To Send | When creating or updating rows, choose whether to automatically map input data fields to table columns or manually specify field values. |
| Inputs To Ignore | When auto-mapping input data, specify any fields to exclude from mapping. |
| Fields UI Field Values | When not auto-mapping, specify individual field names and values to send for create or update operations. Supports binary data upload for attachments. |
| Download Attachments | For get/getAll operations, option to download file attachments from specified fields. |
| Download Field Names | Comma-separated list of field names containing attachments to download when enabled. |
| Return All | For getAll operation, whether to return all matching rows or limit the number returned. |
| Limit | When not returning all rows, specify the maximum number of rows to retrieve. |
| Primary Key | For delete and update operations, select which primary key to use ("id" or custom). |
| Custom Primary Key | If using a custom primary key, specify its name here. |
Output
The node outputs an array of JSON objects representing the rows affected or retrieved:
- Create: Returns the created rows including any IDs assigned by the system.
- Delete: Returns success status per row or errors if deletion failed.
- Get: Returns the requested row's data; optionally includes downloaded binary attachments.
- Get Many: Returns multiple rows as an array; optionally downloads attachments as binary data.
- Update: Returns updated rows or success indicators per row.
If attachments are downloaded, they are included as binary data in the output items alongside the JSON data.
Errors during operations are either thrown or included in the output as error messages depending on the node's "Continue On Fail" setting.
Dependencies
- Requires valid authentication credentials: either an API token or user token configured in n8n.
- Depends on the Lake API endpoints, which vary by selected API version.
- Uses helper functions for API requests and attachment downloads bundled within the node's code.
- Requires network access to the Lake API service.
Troubleshooting
- Error fetching workspaces, bases, or tables: Usually caused by invalid credentials or insufficient permissions. Verify API tokens and user rights.
- Row not found errors: Occur when trying to get, update, or delete a row that does not exist. Check the provided row IDs.
- Attachment upload/download failures: May happen if binary data is missing or malformed. Ensure binary properties are correctly set and accessible.
- API version mismatch: Using incompatible API version settings can cause unexpected errors. Confirm the correct API version matches your Lake instance.
- Empty responses on get operations: Could indicate no matching rows or incorrect parameters. Adjust filters or IDs accordingly.
- Use the node's "Continue On Fail" option to handle errors gracefully in bulk operations.
Links and References
- Lake API Documentation (generic reference, adjust based on actual Lake API docs)
- n8n Expressions Documentation
- n8n Node Development Guide