Lake icon

Lake

Read, update, write and delete data from Lake

Actions5

Overview

The Lake node allows users to interact with a database-like service called "Lake" by performing CRUD (Create, Read, Update, Delete) operations on rows within tables. 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 data for a specific record from a database or spreadsheet-like backend during an automation workflow. For example, you might want to retrieve user details by their unique ID to process or enrich that data further downstream.

Practical examples:

  • Fetching a customer record by ID to send a personalized email.
  • Retrieving a product entry to check stock levels before processing an order.
  • Getting a configuration row to dynamically adjust workflow behavior.

Properties

Name Meaning
Authentication Method of authentication to use: either an API Token or a User Token.
API Version The version of the Lake API to use. Options vary depending on the node setting and include: 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 to operate within.
Base Name or ID (Only for API Version 3) Select or specify the base (project) within the workspace.
Project ID (For API Versions 1 and 2) The project identifier to operate on.
Project Name or ID (For API Version 2) Select or specify the project (base) to operate on.
Table Name or ID The table from which to get the row. Choose from the list or specify an ID. Required.
Table (For API Version 1) The name of the table. Required.
Row ID Value The unique identifier value of the row to retrieve. Required.
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 data of the retrieved row as key-value pairs representing the columns and their values.

If "Download Attachments" is enabled, the node downloads the binary content of the specified attachment fields and includes them in the output's binary property. This allows subsequent nodes to access the actual files attached to the row.

Example output structure (simplified):

{
  "id": "row-id",
  "column1": "value1",
  "column2": "value2",
  "attachmentField": [
    {
      "fileName": "example.pdf",
      "mimeType": "application/pdf",
      "data": "<binary data>"
    }
  ]
}

When attachments are downloaded, the binary data is accessible for further processing or saving.

Dependencies

  • Requires an API authentication token, either via an API Token credential or a User Token credential.
  • Depends on the Lake API endpoints, which differ based on the selected API version.
  • For API Version 3, requires specifying workspace and base (project) IDs.
  • Uses helper methods to handle API requests and optionally download attachments.
  • Requires proper configuration of credentials in n8n to authenticate requests.

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 handle this gracefully, enable "Continue On Fail" to avoid stopping the workflow.
  • Invalid Table or Project: Selecting an incorrect or non-existent table or project/base will cause errors when fetching metadata or rows. Ensure correct selection or expression usage.
  • Attachment Download Issues: If "Download Attachments" is enabled but the field names are incorrect or do not contain attachments, the node may fail or return empty binaries.
  • API Version Mismatch: Using incompatible API versions with certain properties (e.g., workspaceId only available in v3) can cause errors. Verify the API version matches your Lake instance.
  • Authentication Failures: Incorrect or missing API tokens will result in authorization errors. Confirm credentials are set up correctly.

Links and References

Discussion