Overview
This node interacts with a data platform called Lake (NocoDB backend) to perform operations on rows within database tables. Specifically, the "Row" resource with the "Get" operation retrieves a single row by its ID from a specified table in a project or base.
Common scenarios where this node is useful include:
- Fetching detailed information about a specific record in a database table.
- Integrating data retrieval into automated workflows for reporting or further processing.
- Accessing row data dynamically based on input parameters or previous workflow steps.
For example, you might use this node to get customer details by their unique ID from a CRM table, then use that data downstream in your automation.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: either using an API Token or a User Token. |
| API Version | Select the version of the Lake API to use. Options are: Before v0.90.0, v0.90.0 Onwards, and v0.200.0 Onwards. |
| Workspace Name or ID | (Only for API version 3) Select or specify the workspace containing the base. |
| Base Name or ID | (API version 3) Select or specify the base (project) containing the table. |
| Project ID | (API version 1) Specify the project ID. |
| Project Name or ID | (API version 2) Select or specify the project (base). |
| Table Name or ID | Select or specify the table from which to retrieve the row. |
| Row ID Value | The unique identifier value of the row to retrieve. This is required. |
| Download Attachments | Whether to download attachment fields defined in "Download Fields". If enabled, the node will fetch binary data for those fields. |
| Download Fields | Comma-separated list of attachment field names to download if "Download Attachments" is enabled. These must match the exact case-sensitive field names in the table. |
Output
The node outputs JSON data representing the retrieved row. The structure corresponds directly to the columns and values of the row in the specified table.
If "Download Attachments" is enabled, the node also outputs binary data for the specified attachment fields. This allows subsequent nodes to access file contents directly.
Example output JSON structure (simplified):
{
"id": "row-id-value",
"column1": "value1",
"column2": "value2",
"attachmentField": [
{
"filename": "file1.jpg",
"url": "https://..."
}
],
...
}
If attachments are downloaded, the binary data is included alongside the JSON under the binary property.
Dependencies
- Requires connection to the Lake API (NocoDB backend).
- Requires appropriate credentials: either an API token or user token configured in n8n.
- Depending on API version selected, different endpoints are used.
- For downloading attachments, the node makes additional API calls to fetch file content.
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/Base: Selecting or specifying incorrect table or project/base IDs can cause errors fetching metadata or data. Ensure these are correct and accessible with the provided credentials.
- Attachment Download Issues: If "Download Attachments" is enabled but field names are incorrect or the fields do not contain attachments, the node may fail or return empty binary data.
- API Version Mismatch: Using an incompatible API version setting with your Lake instance may cause unexpected errors. Verify the API version matches your server's version.