Overview
This node interacts with a data platform called Lake, specifically focusing on managing rows within tables (referred to as "Row" resource). The "Get Many" operation retrieves multiple rows from a specified table in a project or base. It supports fetching all rows or limiting the number of returned rows, applying sorting and filtering, and optionally downloading attachments linked to the rows.
Common scenarios where this node is beneficial include:
- Extracting bulk data from a database table for reporting or further processing.
- Synchronizing data between Lake and other systems by retrieving updated rows.
- Filtering and sorting data dynamically based on user-defined criteria.
- Downloading file attachments associated with rows for archival or analysis.
Practical example:
- A user wants to retrieve all customer records from a "Customers" table, sorted by last name ascending, and download any attached profile pictures stored in attachment fields.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either an API Token or a User Token. |
| API Version | Selects the version of the Lake API to use. Options are: Before v0.90.0, v0.90.0 Onwards, v0.200.0 Onwards. |
| Workspace Name or ID | (API v0.200.0 Onwards) The workspace context to operate in. Choose from a list or specify an ID via expression. |
| Base Name or ID | (API v0.200.0 Onwards) The base (project) within the workspace. Required. Choose from a list or specify an ID via expression. |
| Project ID | (API Before v0.90.0) The ID of the project. Required. |
| Project Name or ID | (API v0.90.0 Onwards) The project/base to operate on. Required. Choose from a list or specify an ID via expression. |
| Table Name or ID | (API v0.90.0 Onwards) The table to retrieve rows from. Required. Choose from a list or specify an ID via expression. |
| Table | (API Before v0.90.0) The name of the table. Required. |
| Return All | Whether to return all matching rows or limit the results. |
| Limit | Maximum number of rows to return if not returning all. Minimum 1. |
| Download Attachments | Whether to download files from attachment-type fields defined in "Download Fields". |
| Download Fields | Comma-separated list of attachment field names to download. Case sensitive. Required if downloading attachments. |
| Options | Additional options including: - View ID: to select specific fields of the returned rows. - Fields: list of specific fields to return. - Sort: rules defining which fields to sort on and direction. - Filter By Formula: formula string to filter rows. |
Output
The output is a JSON array where each item represents a row retrieved from the specified table. Each row object contains key-value pairs corresponding to the table's columns and their values.
If "Download Attachments" is enabled, the node also outputs binary data for the specified attachment fields, allowing downstream nodes to access the actual files.
Dependencies
- Requires valid authentication credentials: either an API token or a user token.
- Depends on the Lake API endpoints, which vary depending on the selected API version.
- For dynamic loading of workspaces, bases/projects, and tables, the node calls respective API endpoints.
- If downloading attachments, the node performs additional API requests to fetch the files.
- No special environment variables beyond standard n8n credential configuration are required.
Troubleshooting
- Error fetching workspaces/bases/tables: Usually caused by invalid credentials or insufficient permissions. Verify that the API token or user token has access rights.
- Row not found errors: When getting or deleting a row by ID, if the row does not exist, the node throws an error unless "Continue On Fail" is enabled.
- Attachment download failures: Ensure that the specified attachment field names are correct and that the attachments exist. Also verify network connectivity.
- API version mismatch: Selecting an incorrect API version may cause unexpected errors due to endpoint differences. Confirm the API version matches your Lake instance.
- Limit vs Return All: Setting "Return All" to false but specifying a very high limit may lead to partial data retrieval; adjust accordingly.