Update Records Node
Updated
The Update Records node enables you to update field values in one or more records of a selected entity type within an Integration Flow. You can define filter conditions to identify the records that should be updated and specify the fields and values to modify.
Use this node to automate record updates based on workflow events, business rules, or dynamically generated data. For example, you can update a case status, assign records to a specific user, modify custom field values, or synchronize information across records without requiring manual intervention.
Supported Fields
Field | Description |
Name | Enter a unique and descriptive name that identifies the purpose of the node within the Integration Flow. |
Entity Type | Select the entity type whose records you want to update. The available fields and update options are based on the selected entity type. |
Number of Records to Update | Select Single to update one matching record or Multiple to update multiple matching records. You can update up to 100 records in a single execution. |
When the Following Conditions Are Met | Define the conditions that records must satisfy before they are updated. Use AND or OR logic to combine multiple conditions and precisely target the intended records. |
Update the Fields as Following | Specify the fields to update and the values that should be assigned to them when the configured conditions are met. |
Output Variable | Specify a variable to store the updated records. The stored output can be referenced by subsequent nodes in the Integration Flow. |
Exception Variable | Specify a variable to capture technical errors encountered during the update operation. When an exception variable is configured, the node creates separate Success and Failure paths. Technical errors follow the Failure path, while successful executions, including those that return no matching records, follow the Success path. If no exception variable is specified, all outcomes follow the Success path. |
Execution Paths
The execution behavior of the node depends on whether an Exception Variable is configured.
Configuration | Execution Behavior |
Exception Variable is not configured | All execution outcomes follow the Success path. |
Exception Variable is configured | The node creates separate Success and Failure paths to handle execution outcomes. |
Operation completes successfully | The workflow continues through the Success path. |
Technical error occurs | The workflow follows the Failure path, and the exception details are stored in the configured exception variable. |
Operation returns no results | The operation is treated as a successful execution and continues through the Success path. It does not trigger the Failure path. |
Example
Suppose a workflow needs to update the priority of cases that meet a specific condition.
You can configure the Update Records node as follows:
Entity Type: Case
Number of Records to Update: Single or Multiple
Conditions: Select cases that meet the required criteria.
Update Fields: Set the Priority field to the required value.
Output Variable: Store the result for use in subsequent workflow steps.
Exception Variable: Configure this if separate Success and Failure paths are required.
With this configuration, the workflow updates only the cases that satisfy the defined conditions and can continue execution based on the outcome of the operation.