Actions13
Overview
This node interacts with a table resource in the Tulip API to count records based on specified criteria. It is useful when you need to quickly determine how many records exist in a particular table, optionally filtered by certain conditions. For example, you might use it to count how many orders have a status of "pending" or how many machines are currently active.
Properties
| Name | Meaning |
|---|---|
| Table Name or ID | Select the target table from a list or specify its ID using an expression. This determines which table's records will be counted. |
| Limit | Maximum number of results to return. Controls pagination by limiting the number of records considered or returned. |
| Offset | Number of records to skip before starting to count. Useful for paginating through large datasets. |
| Filter | One or more filters to apply to the records before counting. Each filter specifies a column, a comparison function (e.g., equal, not equal, contains), and a value to compare against. Multiple filters can be combined. |
| Filter aggregator | Defines how multiple filters are combined: "All" means every filter must match for a record to be included; "Any" means at least one filter must match. |
The Filter property supports these comparison operators:
- Equal
- Not Equal
- Blank
- Not Blank
- Greater Than or Equal
- Less Than or Equal
- Greater Than
- Less Than
- Contains
- Does Not Contain
- Starts With
- Does Not Start With
- Ends With
- Does Not End With
- Is In List
- Is Not In List
Output
The node outputs JSON data containing the count of records matching the specified filters and pagination parameters. The output structure typically includes a field representing the total number of matched records. There is no binary data output.
Example output JSON snippet:
{
"count": 42
}
Dependencies
- Requires access to the Tulip API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node dynamically loads available tables and columns via helper methods to populate dropdown options.
Troubleshooting
Common issues:
- Incorrect table or column IDs may cause errors or empty results.
- Filters with incompatible data types or invalid values can lead to unexpected counts or failures.
- Pagination parameters (limit and offset) set incorrectly might result in missing records or incomplete counts.
Error messages:
- Authentication errors indicate missing or invalid API credentials; ensure the API key/token is correctly configured.
- "Table not found" or similar errors suggest the specified table ID does not exist or is inaccessible.
- Filter validation errors occur if required filter fields are missing or contain invalid values; verify filter configuration carefully.