Overview
The "Llotus Tables" node integrates with NocoDB, a no-code database platform, to perform various operations on rows within tables. Specifically, the Row - Get Many operation retrieves multiple rows from a specified table in a NocoDB project or base.
This operation is useful when you want to fetch bulk data records for processing, reporting, or integration with other systems. For example, you might use it to:
- Extract all customer records from a CRM table.
- Retrieve filtered and sorted product listings from an inventory table.
- Download attachments linked to rows for further processing.
The node supports advanced options such as filtering rows by formula, sorting results, selecting specific fields, and optionally downloading attachment files associated with the rows.
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 | The workspace context in which the base/project resides (only for API version 3). |
| Base Name or ID | The base or project identifier where the target table exists (required). |
| Project ID | The project identifier (used in older API versions). |
| Table Name or ID | The table from which to retrieve rows (required). |
| 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 specified fields. |
| Download Fields | Comma-separated list of attachment field names whose files should be downloaded (case sensitive). |
| Options | Additional options including: - View ID: To select a specific view's fields. - Fields: List of specific fields to return. - Sort: Rules to sort the returned rows (field and direction). - Filter By Formula: A formula string to filter rows. |
Output
The output is an array of JSON objects representing the rows retrieved from the specified table. Each object corresponds to one row and contains key-value pairs where keys are column names and values are the respective cell data.
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, allowing subsequent nodes to access the file data directly.
Dependencies
- Requires a valid connection to a NocoDB instance.
- Needs either an API token or user token credential configured in n8n for authentication.
- The node uses NocoDB REST API endpoints, so network access to the NocoDB server is necessary.
- For attachment downloads, the node performs additional API calls to fetch binary data.
Troubleshooting
- Empty result or missing rows: Ensure the correct workspace/base/project and table are selected. Verify that any filter formulas are correctly formatted and valid.
- Authentication errors: Confirm that the provided API or user token is valid and has sufficient permissions.
- Attachment download failures: Check that the specified attachment field names are correct and that the attachments exist.
- API version mismatch: Currently, only API version 3 (v0.200.0 onwards) is fully supported for this operation. Using older versions may cause unexpected behavior.
- Rate limits or timeouts: When retrieving large datasets with
Return Allenabled, consider limiting results or adding delays to avoid hitting API rate limits.
Common error messages thrown by the node include:
- Errors related to fetching metadata (workspaces, bases, tables) usually indicate misconfiguration or connectivity issues.
- "The row with the ID ... could not be queried" indicates a non-existent record ID was requested.
- Network or permission errors will surface as API call failures; verify credentials and network access.