Agentic Workflow Field Actions
Audience: Administrators, Developers, Solution Architects
Purpose: Complete reference for the field action types available in Kizen Agentic Workflows, including how to update and clear field values on the context Record and perform arithmetic operations on numeric fields and variables.
Overview
Field actions read from and write to field values on Records and variables. Use them to keep Record data accurate and current as an Agentic Workflow progresses, whether that means updating a single field, clearing multiple fields at once, or computing a new value from existing data.
Note: For error handling, see Agentic Workflow Error Handling.
Change Field Value
The Change Field Value action updates one or more field values on the context Record within a single step. Select one of two operating modes under Choose Action.
Update Field(s): Select the field to update using the Choose Field to Change dropdown, then configure its value source. Use ADD FIELD TO UPDATE to update multiple fields in a single step, which is more efficient than chaining separate steps.
Available value sources:
Specific Value: a hardcoded value set at design time
Field Value on This Record: copies the value from another field on the context record
Field Value on a Related Object: copies the value from a field on a related record
Agentic Workflow Variable: uses a variable value
Agentic Workflow Variable Record Field: uses a field value from a Record-type variable
Blank value: removes the current value from the field
Field resolution options control what happens when the target field already has a value:
Overwrite: replaces the existing value
Only Update Blank: writes the value only if the field is currently empty
Only Add Options: appends the value rather than replacing (applicable to multi-value fields)
Clear Field(s): Clears the value of one or more fields on the context Record in a single step. When a multi-value field such as a tag or multi-select field is included, the builder displays a warning that all values in that field will be removed. Review this carefully before saving.
Change Tags
The Change Tags action adds tags to and removes tags from the context Record in a single step. Both operations are configured on the same action; either can be left empty if only one is needed.
Additional Description: An optional freeform text field for internal notes about the step. This value is not written to the Record.
Choose Tags to Add: A typeahead picker of existing tag options. Select one or more tags to apply to the context Record when the step runs. Tags that are already present on the Record are not duplicated.
Choose Tags to Remove: A typeahead picker of existing tag options. Select one or more tags to remove from the context Record when the step runs. Tags that are not present on the Record are ignored.
Creating a new tag: If a needed tag does not yet exist, it can be created directly from either picker. Selecting the option to add a new tag opens the Add Tag modal, which accepts a tag name and saves the new tag to the tag field's option list. The newly created tag is immediately available for selection in the picker.
Math Operators
The Math Operators action performs arithmetic on numeric values and writes the result to a field or variable. Select Simple Builder under Choose Your Equation Type, then choose one of two operation modes.
Addition/Subtraction: Builds an equation by combining elements using addition and subtraction. Use + ADD ELEMENT to add operands and the Choose Field dropdown to select the output field.
Multiplication/Division: Uses a numerator and denominator layout to represent multiplication and division. Use + ADD ELEMENT to build each row and the Choose Field dropdown to select the output field.
Both modes support the same three element sources: Static Value, Field Value, and Agentic Workflow Variable.The step accepts decimal values. Currency fields are treated as plain numbers.
The Percent Chance to Close field has special handling. It is stored as a decimal internally but displayed as a whole number in the UI. When used in a math step, the system infers whether the input is a decimal (less than 1) or a whole number (between 1 and 100) and adjusts accordingly. Account for this when building formulas that include this field, as it can produce unexpected results if the input source is not considered.
Key Use Cases
Field actions are applicable across any Workflow that requires data to be written, updated, or computed on a Record as part of an automated process. The following examples illustrate common patterns in three industries where accurate, timely field updates are a core operational requirement.
Industry Examples
Insurance Workflows depend on accurate field data at every stage of the policy and claims lifecycle. Field actions keep Records current without requiring manual updates from team members.
Examples include:
Using Change Field Value to update the claim status field to Under Review when a claims Agentic Workflow reaches the adjudication stage
Using Math Operators to calculate a coverage gap value by subtracting the current coverage amount from the requested coverage amount, writing the result to a field for underwriter review
Using Clear Field(s) to remove all pending endorsement fields on a policy Record when the policy is marked as canceled
Using Change Field Value with the Only Update Blank resolution option to set a default adjuster field without overwriting an existing assignment
How field actions help:
Keep status, stage, and classification fields accurate as Records move through automated Workflows without manual intervention
Compute derived values, such as coverage gaps, premium adjustments, or risk scores, directly within an Agentic Workflow rather than relying on external calculation
Enforce data hygiene by clearing stale or irrelevant field values when a Record reaches a terminal state
Apply conditional write logic using field resolution options, preventing Agentic Workflows from overwriting data that has already been set
Healthcare workflows require precise field updates tied to clinical events, intake milestones, and authorization statuses. Field actions ensure that Record data reflects the current state of a patient's workflow at all times.
Examples include:
Using Change Field Value to update a patient Record's care stage field when an intake automation reaches a new phase
Using Math Operators to calculate a patient's days since last contact by subtracting a last contact date variable from the current date, writing the result to a field used for outreach prioritization
Using Clear Field(s) to remove all scheduled appointment fields when a patient Record is marked as discharged
Using Change Field Value to set a risk classification field based on a variable resolved earlier in the Agentic Workflow
How field actions help:
Maintain accurate clinical and administrative field data across patient records without requiring care coordinators to update Records manually
Compute time-based values, such as days since last contact or days until next review, for use in downstream routing and prioritization logic
Clear fields that are no longer relevant when a patient's status changes, reducing noise in care team views and reports
Write classification and status values to Records at the precise point in a workflow when they are determined
Financial services workflows require field updates at every stage of loan origination, compliance review, and account management. Field actions ensure that application and account Records reflect current status, computed values, and regulatory classifications throughout the process.
Examples include:
Using Change Field Value to update a loan application status field to Pending Review when an application is submitted
Using Math Operators to calculate a debt-to-income ratio from two numeric fields on the application record, writing the result to a field used for underwriting routing
Using Clear Field(s) to remove all offer fields on an application Record when the application is withdrawn or declined
Using Change Field Value with a variable source to write a risk tier classification computed earlier in the automation to the account Record
How field actions help:
Keep application and account status fields current at every stage of the origination and review process without manual data entry
Compute regulatory and risk values, such as debt-to-income ratios, loan-to-value ratios, and risk tier classifications, directly within the Agentic Workflow
Enforce data hygiene by clearing offer, approval, and pricing fields when an application reaches a non-qualifying terminal state
Write computed values to fields at the point in the workflow where they are determined, making them available for downstream reporting and routing
What's Next
Continue to Related Object Actions to learn how to create, modify, and archive records associated with the context record, and how to send communications to related Contacts just or check out any of the topics below:
Last updated
Was this helpful?