Overview
This node interacts with a data platform called Lake (NocoDB) to perform operations on rows within database tables. Specifically, the Row Create operation allows users to add new rows of data into a specified table in a project or base.
Common scenarios where this node is beneficial include:
- Automating data entry from other systems or workflows.
- Inserting bulk data records programmatically.
- Integrating form submissions or API data into a structured database.
- Uploading files as part of row data when binary fields are involved.
For example, you could use this node to create new customer records in a CRM table whenever a new lead is captured via a web form, or to insert multiple inventory items into a product catalog table from an external source.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: either using an API Token or a User Token. |
| API Version | Select the API version to use for requests. Options vary by version number: Before v0.90.0, v0.90.0 Onwards, or v0.200.0 Onwards. |
| Workspace Name or ID | (Only for API version 3) Select or specify the workspace where the base/project resides. |
| Base Name or ID | (Only for API version 3) Select or specify the base within the workspace. |
| Project ID | (API versions 1 and 2) Specify the project ID or select from a list (version 2). Required. |
| Table Name or ID | Select or specify the target table where the row will be created. Required. |
| Data to Send | Choose how to provide the data for the new row: - Auto-Map Input Data to Columns: Automatically map incoming JSON properties to matching column names. - Define Below for Each Column: Manually specify each field's value. |
| Inputs to Ignore | (When auto-mapping) Comma-separated list of input fields to exclude from being sent to the table. |
| Fields to Send | (When defining manually) Add one or more fields specifying: - Field Name - Whether the field contains binary data - The value or binary property name containing the file data to upload. |
Output
The output is a JSON array where each item corresponds to a created row. The structure depends on the API version:
- For older API versions (1 and 2), the output includes the original data plus assigned IDs or success indicators.
- For API version 3, the output merges the response data from the server with the submitted data, including any generated fields like record IDs.
If binary files are uploaded as part of the row creation, the node handles uploading these files separately and includes references to them in the created row data.
No binary output is produced by this node; all results are returned as JSON.
Dependencies
- Requires access to the Lake (NocoDB) API endpoint corresponding to the selected API version.
- Requires valid authentication credentials: either an API token or user token.
- For API version 3, workspace and base selection may be required.
- The node uses helper functions to handle API requests and optionally upload binary files.
- Network connectivity to the Lake API service is necessary.
Troubleshooting
Error: "The row with the ID ... could not be queried/updated/deleted."
This indicates that the specified row ID does not exist. Verify the ID values and ensure they correspond to existing rows.Empty or missing response data
Check that the correct project/base and table IDs are selected and that the API version matches your Lake instance.Binary file upload failures
Ensure the binary property names are correct and that the files exist in the input data. Also verify permissions for file uploads.API request errors
Confirm that authentication credentials are valid and have sufficient permissions. Review network connectivity and API endpoint URLs."No Workspace" or "No Base" found when loading options
This usually means the API credentials do not have access to any workspaces or bases, or there is a misconfiguration.
Using the node's "Continue On Fail" option can help process multiple items even if some fail.