Who This Is For / When to Use
This update is for users building workflows that update contact fields based on values calculated or returned earlier in the workflow, especially when working with numeric, monetary, or dropdown-based data.
What’s New in This Update
The Dynamic Custom Value picker can now be used with more contact field types in the Update Contact Field action.
Newly supported field types include:
Numeric fields
Select / Dropdown fields (no option ID required when selecting dynamically)
Monetary fields
This expansion allows workflows to reference live variables instead of hard-coded values when updating contact records.
What Dynamic Custom Values Do
Dynamic Custom Values allow a workflow step to use outputs from earlier steps or existing contact fields as the value being written or compared.
Instead of typing a fixed number or text value, the action pulls the value dynamically at runtime, ensuring the contact field always reflects the latest workflow data.
How to Use Dynamic Values in Update Contact Field
Dynamic values can be applied directly within the Update Contact Field action.
Add an Update Contact Field action to the workflow.
Select the contact field you want to update.
In the value input, switch the right-hand selector to Dynamic Value.
Choose a variable from an earlier workflow step or an existing field.
Select the appropriate operator (number, date, or value-based).
Save and publish the workflow.
The contact field will now update using the live value each time the workflow runs.
How Select / Dropdown Fields Work with Dynamic Values
Select and dropdown fields now support dynamic values without requiring manual entry of option IDs.
When using Dynamic Value selection, the workflow resolves the correct option automatically based on the incoming value, eliminating the need to look up or hard-code IDs in most cases.
This reduces setup time and prevents mismatches caused by renamed or reordered options.
Example Use Case
Dynamic values are useful when workflow logic depends on user responses or calculated results.
For example, after a patient confirms an appointment, the workflow captures the confirmation type (such as Follow-up or New Visit).
The Update Contact Field action then writes this value dynamically into the patient’s contact record, keeping records accurate and ensuring the correct follow-up communications are triggered without manual updates.
Why This Update Matters
This enhancement removes common workflow workarounds and simplifies automation logic.
Key improvements include:
Fewer duplicate fields created solely for comparisons
Cleaner branching logic using existing variables
Consistent behavior with dynamic variables used elsewhere in workflows
Common Issues and Fixes
Dynamic value option is not visible
Ensure the field type is supported and that the right-hand input selector is set to Dynamic Value.
Unexpected value written to a dropdown field
Verify that the dynamic source returns a value that matches one of the dropdown options.
Workflow fails validation after selecting Dynamic Value
Confirm the selected operator matches the field type (number, date, or value).