Actions13
Overview
This node operation allows you to list records from a specified table in the Tulip platform. It is useful when you want to retrieve data entries stored in a Tulip Table, optionally filtered, sorted, and paginated. Common scenarios include fetching recent production data, querying specific machine logs, or extracting subsets of data for reporting or further automation.
For example, you might use this node to:
- Retrieve the last 10 records from a quality control table.
- Get all records where a status column equals "pending".
- Fetch records sorted by timestamp in descending order with pagination support.
Properties
| Name | Meaning |
|---|---|
| Table Name or ID | Select the target table from a dropdown list or specify its ID via an expression. This determines which table's records will be listed. |
| Include Total Count | Boolean flag to include the total number of matching records in the response header. Enabling this triggers an additional query that may impact performance but provides the total count for pagination or display purposes. |
| Limit | Maximum number of records to return in one execution. Useful for controlling batch size or implementing pagination. |
| Offset | Number of records to skip before starting to return results. Used together with Limit for pagination. |
| Sort Options | Allows specifying multiple sorting criteria. For each sort option, select a column (by name or ID) and the direction (ascending or descending). Records are returned ordered accordingly. |
| Filters | Define one or more filters to restrict which records are returned. Each filter specifies a column, a comparison function (e.g., equal, contains, greater than), and a value if applicable. |
| Filter aggregator | Determines how multiple filters are combined: "all" means every filter must match (logical AND), "any" means at least one filter must match (logical OR). |
Output
The output consists of JSON objects representing the records retrieved from the specified table. Each record includes fields corresponding to the table columns with their respective values.
If the "Include Total Count" property is enabled, the total number of matching records is available in the response headers (not directly in the JSON output).
No binary data is output by this node.
Dependencies
- Requires connection to the Tulip API using an API key credential configured in n8n.
- The node depends on the Tulip platform's Tables feature being accessible via the API.
- Proper permissions to read tables and records in Tulip are necessary.
Troubleshooting
- Empty results: Check that the Table Name or ID is correct and that any filters applied do not exclude all records.
- Invalid column names/IDs: When specifying columns for sorting or filtering, ensure they exist in the selected table; otherwise, the request may fail.
- Performance issues: Enabling "Include Total Count" can cause slower responses due to extra queries; disable it if total count is not needed.
- Authentication errors: Verify that the API key credential is valid and has sufficient access rights.
- Pagination mistakes: Ensure that Limit and Offset values are set correctly to avoid missing or duplicate records across multiple executions.