Who This Is For / When to Use
This feature is for Kyrios users who build workflows with conditional logic based on calculated, imported, or previously captured values. It is used when workflow decisions depend on numbers, dates, dropdown selections, or monetary amounts generated earlier in the workflow.
What the Dynamic Custom Value Picker Does
The Dynamic Custom Value Picker allows the right-hand side of an If/Else condition to reference a live variable instead of a static value.
This enables workflows to compare fields against:
Outputs from earlier workflow steps
Stored CRM or Custom Object fields
Values generated by calculations, forms, or webhooks
The comparison updates dynamically at runtime.
Newly Supported Field Types
The If/Else Dynamic Custom Value Picker now supports the following field types:
Numeric fields
Used for scores, counts, quantities, or calculated totals.Date fields
Used for appointment dates, renewal dates, expiration dates, or time-based logic.Select / Dropdown fields
Used for dropdown-based fields that rely on option IDs, not display names.Monetary fields
Used for invoice totals, deal values, proposal amounts, or payment-related logic.
Each field type automatically enforces the correct comparison operators.
How to Use the Dynamic Custom Value Picker in an If/Else Action
Step 1: Add an If/Else Action
In the Workflow Builder, add an If/Else action at the point where branching logic is required.
Step 2: Configure the Left-Hand Field
Select the field you want to evaluate (for example, a contact field, custom value, or calculated output).
Step 3: Switch the Right-Hand Input to Dynamic Value
Change the right-hand input type to Dynamic Value, then select the variable or field generated earlier in the workflow.
Choose an operator that matches the field type (numeric, date, or value-based).
Step 4: Save and Publish
Save the action and publish the workflow.
The workflow will now evaluate conditions using live values at runtime.
Important Notes About Select / Dropdown Fields
Select and dropdown fields use option IDs, not visible labels.
This means:
The condition compares against the internal option ID
Display names (for example, “Won” or “Closed”) will not work
IDs can typically be found via exports, system references, or Kyrios helper documentation
If the option ID does not match, the condition will evaluate as false.
Why This Change Matters
Previously, workflows often required:
Extra fields to store calculated values
Duplicate logic to re-create numbers or dates
Hard-coded comparisons that broke when values changed
Expanded Dynamic Custom Value support removes these workarounds by allowing workflows to branch directly on the same variable already in use, using a consistent merge-field and variable model across Kyrios.
Example Use Case
High-Value Proposal Routing
A workflow receives a proposal value from a form submission or webhook and stores it as a dynamic monetary value.
If the value is greater than or equal to $25,000, the workflow assigns the record to a senior partner and flags it for priority follow-up.
If the value is less than $25,000, the workflow continues through the standard process.
No static numbers or duplicated fields are required.
Common Issues and Fixes
Condition never evaluates as true
Cause: The field type or operator does not match the dynamic value type.
Fix: Ensure numeric fields use numeric operators, date fields use date operators, and dropdowns use option IDs.
Dropdown condition fails unexpectedly
Cause: The condition uses the display name instead of the option ID.
Fix: Replace the display name with the correct option ID.
Dynamic value does not appear in the picker
Cause: The value has not been generated earlier in the workflow.
Fix: Confirm the variable or field is created or populated before the If/Else action.