Overview
This node allows you to create rows in a specified table within a project (or base) on the Lake platform. It supports multiple API versions and authentication methods, enabling flexible integration with different Lake environments.
Common scenarios include:
- Automatically adding new records from form submissions or other data sources.
- Inserting bulk data into a database table for further processing.
- Uploading files as part of row creation when binary data is involved.
For example, you can use this node to add new customer entries to a CRM table or log sensor data into a time-series database table.
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 resides. |
| Base Name or ID | (Only for API version v0.200.0 Onwards) Select or specify the base (project) containing the target table. |
| Project ID | (For older API versions) Specify the project ID where the table exists. |
| Table Name or ID | Select or specify the table where the new row(s) will be created. |
| Data to Send | Choose how to provide data for the new row(s): - Auto-Map Input Data to Columns: Automatically map incoming JSON fields to table columns (field names must match). - Define Below for Each Column: Manually specify each column's value. |
| Inputs to Ignore | (When using auto-map mode) Comma-separated list of input properties to exclude from being sent to the table. Leave empty to send all. |
| Fields to Send | (When defining fields manually) Add one or more fields specifying: - Field Name - Whether the field contains binary data - Field Value (for non-binary) - Binary Property name (for binary data) |
Output
The node outputs an array of JSON objects representing the created rows. The structure depends on the API version:
- For API versions before v0.200.0, the output includes the original data plus assigned IDs.
- For v0.200.0 onwards, the output merges the response data with the sent data, reflecting the newly created records including any server-generated fields.
If binary data was uploaded as part of the row creation, the node handles uploading files to storage endpoints and includes references to these uploads in the respective fields.
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 API version.
- Uses helper functions to upload binary files if included in the row data.
- Requires network access to the Lake API endpoints.
Troubleshooting
- Error creating rows: Could be due to invalid project/base/table IDs or insufficient permissions. Verify that the selected workspace, base/project, and table exist and that your credentials have write access.
- Field mapping issues: When using auto-map mode, ensure input JSON field names exactly match the destination table column names. Use an "Edit Fields" node beforehand if necessary.
- Binary file upload failures: Confirm that the binary property names are correct and that the files are accessible. Also, check API version compatibility for storage upload endpoints.
- API version mismatch: Selecting the wrong API version may cause endpoint errors. Confirm the Lake instance version and select the matching API version in the node settings.
- Continue on Fail behavior: If enabled, the node will continue processing remaining items even if some fail, returning error details per item.
Links and References
- Lake API Documentation (generic placeholder)
- n8n Expressions Documentation
- n8n Binary Data Handling