Overview
The node "Llotus Tables" integrates with NocoDB to perform CRUD operations on rows within database tables. Specifically, the Row Create operation allows users to add new rows to a specified table in a NocoDB base (project). This is useful for automating data entry, syncing external data sources into NocoDB, or programmatically managing records.
Common scenarios include:
- Automatically inserting form submission data into a NocoDB table.
- Creating new inventory or customer records from an external system.
- Uploading files as attachments linked to newly created rows.
For example, you might use this node to create a new row in a "Contacts" table with fields like Name, Email, and Phone populated from previous workflow steps.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: either using an API Token or a User Token to connect to NocoDB. |
| API Version | Select the API version to use; currently only version 3 (v0.200.0 onwards) is supported. |
| Workspace Name or ID | The workspace in NocoDB where the base (project) resides. Can be selected from a list or specified via expression. |
| Base Name or ID | The base (project) within the workspace containing the target table. Required field. Can be selected from a list or specified via expression. |
| Table Name or ID | The table within the base where the new row will be created. Required field. Can be selected from a list or specified via expression. |
| Data to Send | How to provide the data for the new row: - Auto-Map Input Data to Columns: Automatically map incoming JSON properties to columns with matching names. - Define Below for Each Column: Manually specify each column's value. - Use Table Schema: Select fields from the table schema and assign values. |
| Inputs to Ignore | When using auto-mapping, specify input property names to exclude from being sent to NocoDB, separated by commas. Leave empty to send all properties. |
| Fields to Send | When manually defining fields, specify each field name and its value. Supports binary data upload by specifying a binary property containing the file data. |
| Fields (Use Schema) | When using the table schema mode, select fields from the table and specify their values. |
Output
The output of the node is a JSON array where each element corresponds to a created row. Each JSON object contains the data returned by NocoDB after creating the row, typically including the new row's ID and any other fields stored in the table.
If binary data (files) are uploaded as part of the row creation, the node handles uploading these files to NocoDB's storage and associates them with the respective fields. The output JSON includes references to these uploaded files.
Dependencies
- Requires access to a NocoDB instance with appropriate permissions.
- Needs either an API token or user token credential configured in n8n for authentication.
- Uses NocoDB REST API v0.200.0 onwards (API version 3).
- For binary file uploads, the node performs multipart/form-data POST requests to NocoDB's storage upload endpoint.
Troubleshooting
- Authentication errors: Ensure that the provided API token or user token is valid and has sufficient permissions to create rows in the target base and table.
- Invalid table or base selection: If the base or table ID/name is incorrect or missing, the node will fail. Use the load options dropdowns or expressions carefully.
- Field mapping issues: When using auto-map mode, ensure input JSON keys exactly match the column names in NocoDB. Use an "Edit Fields" node before this node if necessary to rename fields.
- Binary upload failures: Verify that the binary property specified contains valid file data. Also, check that the NocoDB storage upload endpoint is accessible and that the project/base ID is correct.
- API errors: The node throws detailed errors when API calls fail. Enable "Continue On Fail" to handle errors gracefully and inspect error messages in the output.
Links and References
- NocoDB Official Documentation
- n8n Expressions Documentation
- NocoDB API Reference (for understanding endpoints used)