Overview
This node allows users to delete rows from a NocoDb table. It supports multiple API versions of NocoDb and different authentication methods (API token or user token). The node is useful when you want to programmatically remove specific records from your NocoDb database based on their unique identifiers.
Common scenarios include:
- Cleaning up outdated or incorrect data entries.
- Automating deletion of records after processing.
- Integrating with other workflows where removal of database rows is required.
For example, you might use this node in a workflow that deletes user records after they unsubscribe from a service, or removes temporary data after a batch process completes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: "API Token" or "User Token". |
| API Version | Select the version of the NocoDb API 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 3) Select or specify the workspace by name or ID. |
| Base Name or ID | (Only for API version 3) Select or specify the base (project) by name or ID. |
| Project ID | (For API versions 1 and 2) Specify the project ID as a string or select from a list. |
| Table Name or ID | Select or specify the table from which to delete rows. |
| Primary Key Type | Defines the primary key field type used to identify rows: "Default" (id), "Imported From Airtable" (ncRecordId), or "Custom" (specify custom primary key field name). |
| Field Name | (Shown if Primary Key Type is "Custom") Specify the name of the custom primary key field. |
| Row ID Value | The value of the primary key field identifying the row to delete. Required for each item processed. |
Output
The output is a JSON array representing the result of the delete operation for each input item:
- For API version 1, the output simply returns the original input items.
- For API version 2, the output is an array indicating success or failure per item. If a row could not be deleted (e.g., it does not exist), an error message is returned unless "Continue On Fail" is enabled.
- For API version 3, the output contains the raw response from the delete API call.
No binary data is output by this node.
Dependencies
- Requires access to a NocoDb instance with appropriate permissions.
- Requires either an API token or user token credential configured in n8n for authentication.
- The node dynamically calls NocoDb REST API endpoints depending on the selected API version.
- For API version 3, workspace and base selection are required to construct correct API paths.
Troubleshooting
- Row Not Found Error: If the specified row ID does not exist, the node throws an error unless "Continue On Fail" is enabled. Verify the row ID is correct and exists in the target table.
- Authentication Errors: Ensure the provided API token or user token has sufficient permissions to delete rows.
- Incorrect API Version: Using the wrong API version setting may cause endpoint errors. Confirm the NocoDb server version and select the matching API version.
- Missing Required Parameters: The node requires project/base ID, table name/ID, and row ID values. Missing any of these will cause errors.
- Custom Primary Key Issues: When using a custom primary key, ensure the field name matches exactly the primary key field in the table.
Links and References
- NocoDb Official Documentation
- NocoDb API Reference
- n8n Expressions Documentation (for dynamic parameter values)