NocoDb (Upsert) icon

NocoDb (Upsert)

Read, update, write and delete data from NocoDb
Join our community

Actions6

Overview

This node interacts with rows in a NocoDb table, specifically supporting the "Get" operation on the "Row" resource. It retrieves a single row from a specified table by its ID. The node supports multiple API versions of NocoDb and can optionally download attachment fields associated with the row.

Common scenarios where this node is beneficial include:

  • Fetching detailed data for a specific record in a NocoDb table.
  • Retrieving attachments linked to a row for further processing or storage.
  • Integrating NocoDb data retrieval into automated workflows, such as syncing data with other systems or triggering actions based on row content.

Practical example:

  • You have a project management base in NocoDb and want to fetch details of a particular task (row) by its ID, including any attached files like screenshots or documents, to process them in your workflow.

Properties

Name Meaning
Authentication Method of authentication to use: either an API Token or a User Token.
API Version The version of the NocoDb API to use. Options are: 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 containing the base/project.
Base Name or ID (API version 2 and 3) Select or specify the base/project within the workspace. Required for these versions.
Project ID (API version 1) The ID of the project (equivalent to base in newer versions). Required for version 1.
Table Name or ID The table from which to retrieve the row. For API versions 2 and 3, selectable from a list depending on the selected project/base. For version 1, the table name as string. Required.
Row ID Value The unique identifier value of the row to retrieve. Required.
Download Attachments Boolean flag indicating whether to download attachment fields defined in "Download Fields". Only applicable for the "get" operation.
Download Fields Comma-separated list of field names of type 'attachment' that should be downloaded if "Download Attachments" is enabled. Case sensitive. Required if downloading attachments.

Output

The node outputs JSON data representing the retrieved row(s):

  • The json output contains the key-value pairs of the row's fields as stored in NocoDb.
  • If "Download Attachments" is enabled, the node also downloads the specified attachment fields and includes their binary data in the output under the binary property. This allows subsequent nodes to access the actual file contents.
  • Each item corresponds to one input item processed, preserving execution metadata.

Dependencies

  • Requires access to a NocoDb instance with appropriate permissions.
  • Needs 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 attachment downloads, it uses 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 stating the row could not be queried. To handle this gracefully, enable "Continue On Fail" to capture errors per item.
  • Invalid Table or Project/Base: Selecting a non-existent or incorrect table or project/base ID will cause API errors. Ensure correct selections or expressions are used.
  • Attachment Download Issues: If attachment fields are incorrectly named or do not contain attachments, the download may fail or return empty data.
  • API Version Mismatch: Using an incompatible API version setting with your NocoDb instance may result in endpoint errors. Verify your NocoDb version and select the matching API version in the node settings.
  • Authentication Errors: Invalid or missing credentials will cause authentication failures. Confirm that the API token or user token is valid and has sufficient permissions.

Links and References

Discussion