Delete Records Node
Updated
The Delete Records node allows you to permanently remove one or multiple records associated with a specified entity type directly from within a workflow. Rather than requiring manual cleanup or a separate backend process, this node lets you identify exactly which records should be removed using filters and execute the deletion as part of an automated flow.
To configure it, you define the Entity Type, apply Filters to identify the records you want to delete, and specify an Output Variable to capture the response. Upon execution, the node removes the filtered records from Sprinklr's database and stores the status or outcome of the operation in the designated output variable, which can then be used to drive further logic downstream.
How It Works
When the workflow reaches this node, it evaluates the configured filter conditions against records of the selected entity type. Any record matching those conditions is deleted from Sprinklr's database. Because this action is irreversible, the node is intentionally built around precise, filter-driven targeting rather than broad or open-ended deletion; you always control exactly which records are affected before the operation runs.
The outcome of the deletion - success, failure, or the number of records affected- is captured through the node's output and exception variables, allowing subsequent nodes in the workflow to respond appropriately.
Supported Fields
Field | Description |
Name | Enter a unique and descriptive name that identifies the purpose of the node. |
Entity Type | Select the entity type whose records you want to delete. Deletion is currently supported only for Screen Recording and Custom entities. |
Number of Records to Delete | Select Single to delete one matching record or Multiple to delete multiple matching records. You can delete up to 100 records in a single execution. |
Filter Records | Define the conditions that identify the records to delete. Use AND or OR logic to combine multiple conditions and narrow the selection. |
Exception Variable | Specify a variable to capture technical errors encountered during deletion. When an exception variable is configured, the node creates separate Success and Failure paths.
Technical errors follow the Failure path, while a successful operation, including one in which no matching records are found, follows the Success path. If you do not specify an exception variable, all outcomes follow the Success path. |
Entity Support and Limitations
Deletion is currently limited to the Screen Recording and Custom entity types. Other entity types, such as Case, are not yet supported for deletion through this node.
A maximum of 100 records can be deleted in a single execution. Larger sets of records would need to be processed in batches across multiple executions.
Filter values accept only String values, not numbers, and must be entered within double quotes.
Best Practices
Configure the Delete Records node carefully to ensure that only the intended records are removed:
Validate Records Before Deletion: Use a Get Records or Count Records node earlier in the workflow to verify which records match the configured filter conditions and how many records will be affected before proceeding with the deletion.
Use Precise Filter Conditions: Configure specific filter criteria to ensure that only the intended records are deleted. Broad or loosely defined conditions can increase the risk of unintended record removal.
Configure an Exception Variable: Define an Exception Variable to capture technical errors and route execution through a dedicated Failure path. This helps distinguish actual failures from successful executions.
Track Deletion Outcomes: Store or log the outcome of the deletion operation to maintain visibility into workflow activity and support auditing, monitoring, and troubleshooting.
Test Before Deployment: Validate the workflow in a controlled environment before deploying it to production, especially when working with Custom entities or complex filter conditions.
Common Use Cases
Remove Obsolete Screen Recordings: Delete expired or outdated screen recordings that are no longer required for compliance, auditing, or review purposes.
Clean Up Temporary Custom Records: Remove records created in custom entities as part of temporary workflows, testing activities, or proof-of-concept implementations.
Automate Data Hygiene: Incorporate record deletion into scheduled or event-driven workflows to maintain data quality and reduce the need for manual cleanup activities.