Overview
This node enables creating rows in a specified table within a project (or base) on the Lake platform. It supports multiple API versions and authentication methods, allowing users to insert new data records programmatically.
Common scenarios include:
- Automating data entry into a database table.
- Integrating external data sources by mapping incoming data fields directly to table columns.
- Uploading binary files as part of row creation, such as attachments or images.
Practical example:
- A user receives form submissions via a webhook and wants to create corresponding rows in a Lake table with the submitted data.
- Automatically adding product information including images to an inventory table by uploading binary files alongside textual data.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests: either using an API Token or a User Token. |
| API Version | 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 v0.200.0 onwards) Select or specify the workspace containing the base/project. |
| Base Name or ID | (Only for API v0.200.0 onwards) Select or specify the base (project) where the table resides. |
| Project ID | (For API versions before v0.200.0) Specify the project ID where the table is located. |
| Project Name or ID | (For API v0.90.0 onwards) Select or specify the project/base name or ID. |
| Table Name or ID | Select or specify the target table where the new row(s) will be created. |
| Data to Send | How to provide data for the new row(s): - Auto-Map Input Data to Columns: Automatically map input JSON properties to matching column names. - Define Below for Each Column: Manually specify each field. |
| Inputs to Ignore | (When auto-mapping) Comma-separated list of input fields 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: Target column name. - Is Binary File: Whether this field contains binary data. - Field Value or Binary Property: Value or binary property name to upload. |
Output
The node outputs an array of JSON objects representing the created rows. The structure depends on the API version:
- For older API versions, the output includes the original data plus assigned IDs.
- For newer API versions, the output includes the full response from the API, which may contain additional metadata about the created records.
If binary files are uploaded as part of the row creation, the node handles the upload separately and stores references to these files in the respective fields as JSON strings.
No direct binary output is produced by this node; binary data is only used internally during upload.
Dependencies
- Requires valid authentication credentials: either an API token or a user token.
- Depends on the Lake API endpoints, which vary by selected API version.
- Uses helper functions to perform HTTP requests and handle binary data uploads.
- For API v0.200.0 onwards, requires selecting workspace and base (project) to correctly resolve endpoints.
Troubleshooting
Error: "The row with the ID ... could not be queried/updated/deleted."
This indicates the specified row ID does not exist. Verify the ID is correct and exists in the target table.Empty or missing required parameters (e.g., projectId, table)
Ensure all required fields are filled and valid. Use expressions if dynamic values are needed.Binary file upload failures
Confirm that the binary property specified exists and contains valid binary data. Also, check API permissions for file uploads.API version mismatch errors
Make sure the selected API version matches the Lake instance's supported version to avoid endpoint or payload incompatibilities.Network or authentication errors
Verify that the provided API token or user token is valid and has sufficient permissions.
Links and References
- Lake API Documentation (generic reference, adjust based on actual Lake API docs)
- n8n Expressions Documentation
- Handling Binary Data in n8n