Overview
The "Lake" node enables interaction with a data platform called Lake, allowing users to perform CRUD (Create, Read, Update, Delete) operations on rows within tables of projects or bases. Specifically, the "Row - Get" operation retrieves a single row from a specified table by its ID.
This node is useful in scenarios where you need to fetch detailed information about a specific record from a database-like service during an automation workflow. For example, you might want to retrieve customer details by their unique ID before processing an order or updating related records.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "API Token" or "User Token". |
| API Version | The version of the Lake API to use. Options depend on the selected version: - Before v0.90.0 - v0.90.0 Onwards - v0.200.0 Onwards |
| Workspace Name or ID | (Only for API version 3) Select or specify the workspace to operate in. |
| Base Name or ID | (Only for API version 3) Select or specify the base (project equivalent) within the workspace. |
| Project ID | (For API versions 1 and 2) The project identifier. For version 2, can be selected from a list. |
| Table Name or ID | The table from which to get the row. Can be selected from a list or specified by ID. Required for API versions 2 and 3. |
| Table | (For API version 1) The name of the table. |
| Row ID Value | The unique identifier value of the row to retrieve. Required for all API versions. |
| Download Attachments | Whether to download attachment fields defined in "Download Fields". Only applicable for the "get" operation. |
| Download Fields | Comma-separated list of attachment field names to download if "Download Attachments" is enabled. Case sensitive. |
Output
- The output JSON contains the retrieved row's data as key-value pairs representing the columns and their values.
- If "Download Attachments" is enabled, the node downloads the binary content of specified attachment fields and includes them in the output's binary data section.
- The output is structured as an array of items, each containing the JSON data of the row and optionally binary attachments.
Dependencies
- Requires connection to the Lake API service.
- Needs appropriate authentication credentials: either an API token or a user token.
- Depending on the API version, different endpoints are used.
- The node uses helper methods to handle API requests and downloading attachments.
- Requires n8n environment configured with the necessary credentials for authentication.
Troubleshooting
- Row Not Found Error: If the specified row ID does not exist, the node throws an error indicating the row could not be queried. To resolve, verify the row ID is correct and exists in the specified table.
- Authentication Failures: Ensure that the provided API token or user token is valid and has sufficient permissions.
- Incorrect Table or Project/Base Selection: Selecting the wrong table or project/base will cause errors or empty results. Double-check selections or IDs.
- Attachment Download Issues: If attachments fail to download, confirm that the field names are correctly specified (case sensitive) and that the attachments exist.
- API Version Mismatch: Using incompatible API versions may cause unexpected errors. Confirm the API version matches your Lake instance.
Links and References
- n8n Expressions Documentation
- Lake API documentation (refer to your Lake service provider for official API docs)