Actions13
Table → Count Records
AI-generatedOverview
This node interacts with a table resource in the Tulip API to count records based on specified criteria. It allows users to specify a table, apply filters on columns, and retrieve the count of records that match those filters. This is useful for scenarios where you need to quickly determine how many entries meet certain conditions without retrieving all data, such as monitoring inventory levels, counting active orders, or summarizing filtered datasets.
Practical examples:
- Counting how many products have stock below a threshold.
- Determining the number of open support tickets assigned to a specific team.
- Getting the total number of records created after a certain date.
Properties
| Name | Meaning |
|---|---|
| Table Name or ID | Select the target table from a list or specify its ID via an expression. |
| Limit | Maximum number of results to return (used for pagination). |
| Offset | Number of records to skip before starting to return results (used for pagination). |
| Filter | One or more filters to apply on the table's columns. Each filter includes: - Column Name or ID: The column to filter on. - Function: Comparison operator (e.g., Equal, Not Equal, Contains, Greater Than, etc.). - Value: The value to compare against. |
| Filter aggregator | How multiple filters are combined: - All: Every filter must match for a record to be counted. - Any: At least one filter must match for a record to be counted. |
Output
The output contains a JSON object with the count of records matching the specified filters. The structure typically includes a field representing the total count of matched records.
If binary data were involved (not indicated here), it would represent file contents or attachments related to the records, but this operation focuses solely on numeric counts.
Dependencies
- Requires access to the Tulip API with appropriate authentication via an API key credential.
- The node depends on the ability to load tables and columns dynamically from the Tulip environment.
- Proper configuration of the API credentials within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing table ID/name: Ensure the table exists and is correctly referenced.
- Incorrect filter definitions: Verify column names/IDs and filter values are valid and compatible with the selected comparison operators.
- API authentication errors: Confirm that the API key credential is valid and has sufficient permissions.
- Pagination parameters (limit and offset) out of range or invalid: Use non-negative integers.
Error messages:
- "Table not found" or similar: Check the table identifier.
- "Invalid filter function" or "Filter value missing": Review filter configurations.
- Authentication failures: Revalidate API credentials.
Resolving these usually involves verifying input parameters and ensuring proper API access rights.