Overview
This node integrates with NocoDB to perform operations on rows within database tables. Specifically, the "Row" resource with the "Get" operation allows users to retrieve a single row by its ID from a specified table in a NocoDB project.
Common scenarios where this node is beneficial include:
- Fetching detailed data of a specific record for further processing or decision-making.
- Integrating NocoDB data retrieval into automated workflows, such as syncing data with other systems.
- Downloading attachments associated with a row's fields for use in downstream tasks.
Practical example:
- A workflow that triggers when a new order ID is received and uses this node to fetch the full order details from NocoDB, optionally downloading any attached invoices or documents.
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 (currently only v0.200.0 onwards supported). |
| Workspace Name or ID | Select or specify the workspace containing the project (only relevant for API version 3). |
| Base Name or ID | Select or specify the base/project within the workspace to operate on (required). |
| Table Name or ID | Select or specify the table from which to get the row (required). |
| Row ID Value | The unique identifier value of the row to retrieve (required). |
| Download Attachments | Boolean option to indicate whether attachment-type fields defined in "Download Fields" should be downloaded. |
| Download Fields | Comma-separated list of attachment field names to download if "Download Attachments" is enabled. These must match exactly the field names in NocoDB and are case sensitive. |
Output
The output JSON contains the data of the retrieved row as returned by the NocoDB API. This includes all fields of the row with their values.
If "Download Attachments" is enabled, the node also downloads the binary content of the specified attachment fields and includes them in the output under the binary property. This allows subsequent nodes to access the actual files linked to the row.
Dependencies
- Requires connection to a NocoDB instance via either an API token or user token authentication.
- Needs proper configuration of credentials in n8n to authenticate API requests.
- Uses NocoDB REST API endpoints to fetch metadata (workspaces, bases, tables) and row data.
- For attachment downloads, it relies on additional internal helper functions to fetch and attach binary data.
Troubleshooting
- Row Not Found: If the specified row ID does not exist, the node throws an error indicating the row could not be queried. To handle this gracefully, enable "Continue On Fail" to avoid workflow interruption.
- Invalid Table or Project: Selecting a non-existent or incorrect table/base will cause errors fetching metadata or rows. Ensure correct IDs or names are used.
- Attachment Download Issues: If attachment fields are incorrectly named or do not contain attachments, downloads may fail or return empty results.
- API Version Mismatch: Using unsupported API versions or mismatched parameters can cause request failures.
- Authentication Errors: Invalid or missing API tokens/user tokens will prevent successful API calls.
To resolve these issues:
- Verify all IDs and names against your NocoDB instance.
- Check authentication credentials are valid and have sufficient permissions.
- Use expressions carefully to ensure dynamic values are correct.
- Enable "Continue On Fail" during testing to capture errors without stopping the workflow.
Links and References
- NocoDB Official Documentation
- n8n Expressions Documentation
- NocoDB API Reference (for understanding API endpoints used)