Overview
This node interacts with NocoDB to manage rows within tables. Specifically, the "Delete" operation for the "Row" resource allows users to delete one or multiple rows from a specified table in a NocoDB base (project). This is useful when you want to programmatically remove data entries based on their primary key values.
Common scenarios include:
- Cleaning up outdated or incorrect records automatically.
- Removing test data after processing.
- Managing data lifecycle by deleting rows that meet certain criteria.
Example: Deleting a row with a specific ID from a table named "Customers" in a project.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: either an API Token or a User Token to connect to NocoDB. |
| API Version | The version of the NocoDB API to use. Currently supports "v0.200.0 Onwards". |
| Workspace Name or ID | Select or specify the workspace containing the base/project. |
| Base Name or ID | Select or specify the base (also called project) where the table resides. Required. |
| Table Name or ID | Select or specify the table from which rows will be deleted. Required. |
| Primary Key Type | Defines the type of primary key field used to identify rows: - Default ( id): standard primary key added by NocoDB UI.- Imported From Airtable ( ncRecordId).- Custom: specify a custom primary key field name. |
| Field Name (customPrimaryKey) | If "Custom" primary key type is selected, specify the exact field name used as the primary key. |
| Row ID Value (id) | The value(s) of the primary key identifying the row(s) to delete. Required. Can be provided per item if multiple inputs are processed. |
Output
The output is a JSON array representing the result of the delete operation for each input item. Each element corresponds to a deleted row and contains the response from the NocoDB API confirming deletion.
If multiple rows are deleted at once, the output array includes all responses spread into it.
No binary data is produced by this operation.
Dependencies
- Requires access to a NocoDB instance with appropriate permissions.
- Requires either an API token or user token credential configured in n8n for authentication.
- Uses NocoDB REST API endpoints to perform operations.
- The node depends on n8n's helper functions for making authenticated HTTP requests and handling input/output data.
Troubleshooting
Error: Row not found or does not exist
This can occur if the provided primary key value does not match any existing row. Verify the ID value and ensure the correct table and base are selected.Authentication errors
Ensure the API token or user token is valid and has sufficient permissions to delete rows.Incorrect primary key field
If using a custom primary key, make sure the field name matches exactly the column name in NocoDB.Empty or missing required parameters
The node requires the project/base ID, table ID, and row ID(s). Missing these will cause errors.API version mismatch
Using an unsupported API version may cause unexpected errors. Use the supported version indicated in the properties.
Links and References
- NocoDB Official Documentation
- NocoDB API Reference
- n8n Expressions Documentation (for dynamic parameter values)