Count Records Node
Updated
The Count Records node enables you to retrieve the count of records associated with a particular entity. To use it, you specify the Entity Type, apply Filters, and assign an Output Variable. When the node is executed, the output variable holds the count of records linked to the specified entity, based on the applied filters.
How It Works
When the workflow reaches this node, it queries Sprinklr's database for records matching the selected entity type and the configured filter conditions. Rather than returning the records themselves, it returns only the total number of matching records, which is stored in the assigned output variable for use elsewhere in the workflow.
Supported Fields
Field | Description |
Name | Enter a unique and descriptive name for the node. |
Entity Type | Select the entity type whose records you want to count, such as cases, screen recordings, tasks, or another supported entity. |
Filter Records | Define filters to count only the records that meet the specified conditions. Use AND or OR logic to combine multiple conditions. |
Output Variable | Specify an output variable to store the record count for use in subsequent nodes or decisions. |
Exception Variable | Specify a variable to capture technical errors encountered during the count operation. |
Note: Filter values accept only String values, not numbers, and must be entered within double quotes.
Success and Failure Paths
By default, the Count Records node routes all outcomes, including a count of zero, down a single path. If you want to distinguish between a successful count operation and a technical failure, define an Exception Variable. Doing so creates two distinct paths:
Success Path: executed when the count operation completes successfully, regardless of whether the count is zero or a positive number.
Failure Path: triggered only when the operation encounters a technical error.
Use Cases
The Count Records node is commonly used to:
Check how many open cases exist for a customer before deciding how to route a workflow.
Validate whether a threshold has been crossed (e.g., more than a certain number of records matching a condition) before triggering an action.
Feed a count into a Decision Box node to branch the workflow based on volume.