Overview
This node interacts with a database-like service called Lake (NocoDB) to manage rows in tables. Specifically, the "Row" resource with the "Get Many" operation retrieves multiple rows from a specified table. It supports filtering, sorting, selecting specific fields, and optionally downloading attachments linked to those rows.
Common scenarios include:
- Fetching bulk data from a table for reporting or further processing.
- Retrieving filtered and sorted datasets based on custom formulas or views.
- Downloading file attachments associated with rows for backup or analysis.
Practical example:
- A user wants to get all customer records from a "Customers" table, sorted by last purchase date descending, only retrieving the name and email fields, and download any attached profile pictures.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between two authentication methods: "API Token" or "User Token". |
| API Version | Select the API version 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 v0.200.0 Onwards) Select or specify the workspace to operate within. |
| Base Name or ID | (Only for API version v0.200.0 Onwards) Select or specify the base (project) within the workspace. |
| Project ID | (For older API versions) Specify the project identifier. |
| Project Name or ID | (For API version v0.90.0 Onwards) Select or specify the project/base. |
| Table Name or ID | Select or specify the table from which to retrieve rows. |
| Return All | Whether to return all matching rows or limit the number of results. |
| Limit | Maximum number of rows to return if not returning all. |
| Download Attachments | Whether to download attachment files defined in the "Download Fields" property. |
| Download Fields | Comma-separated list of field names of type 'attachment' whose files should be downloaded. Case sensitive. |
| Options | Additional options as a collection: |
| - View ID | Specify a view ID to select particular fields or filter preset in that view. |
| - Fields | List of specific fields to return for each row. |
| - Sort | Sorting rules, each specifying a field and direction (ascending or descending). |
| - Filter By Formula | A formula string to filter rows, e.g., (name,like,example%)~or(name,eq,test). |
Output
The output is an array of JSON objects representing the retrieved rows from the specified table. Each object contains key-value pairs corresponding to the fields requested or all fields if none specified.
If "Download Attachments" is enabled, the node also downloads the binary content of the specified attachment fields and includes them in the output's binary data section, allowing subsequent nodes to access the files directly.
Dependencies
- Requires valid authentication via either an API token or user token credential.
- Depends on the Lake (NocoDB) API endpoints, which vary depending on the selected API version.
- For downloading attachments, the node makes additional API calls to fetch file contents.
- The node uses internal helper functions to handle pagination when "Return All" is true.
Troubleshooting
- Empty or missing rows: Ensure the correct project/base, table, and filters are set. Verify that the API version matches your Lake instance.
- Attachment download failures: Confirm that the specified "Download Fields" exist and are of attachment type. Also, check network connectivity and permissions.
- API errors about missing IDs or permissions: Double-check authentication credentials and that the user has access to the workspace/project/table.
- Limit ignored when "Return All" is true: This is expected behavior; disable "Return All" to enforce limits.
- Formula syntax errors: The filter formula must follow the expected syntax; invalid formulas may cause API errors.
Links and References
- NocoDB API Documentation
- n8n Expressions Documentation
- Lake Node GitHub Repository (for source and updates)