Fix: Create/Update Record Picklists Now Accept Dynamic Values
TL;DR
Picklist fields in 'Create/Update Record' actions now support dynamic values via a Standard/Dynamic toggle.
TL;DR
HighLevel fixed an issue where picklist fields in 'Create/Update Record' workflow actions couldn't use dynamic values. There's now a toggle to switch between standard searchable picklists and dynamic input for merge tags. No immediate action required, but check your existing workflows if you use these actions.
Who this affects
This primarily affects agency owners and SaaS entrepreneurs who build advanced workflows using the 'Create/Update Record' action. If you needed to dynamically set single-select dropdown fields based on contact data or other merge tags, this update is for you. If your workflows only use static values for these fields, or you don't use this specific action, you can safely ignore this.
What changed
HighLevel has updated the 'Create/Update Record' action within the workflow builder. The key changes are:
- Single-select dropdown fields in 'Create/Update Record' actions now have a Standard and Dynamic toggle.
- Standard mode provides a searchable picklist with image options, as you'd expect.
- Dynamic mode provides a text input with a custom value picker for merge tags.
- Saved values that do not match existing picklist options will now open in Dynamic mode by default.
- Switching between Standard and Dynamic modes will clear the field value, so be mindful when adjusting.
HighLevel has not confirmed who is affected, whether this replaces or breaks existing functionality, any limits or plan gating, or the rollout status.
Where to find it
This enhancement is located within the workflow builder:
Automations > Workflow Builder > Actions > Create Record / Update Record
When you add or edit a 'Create Record' or 'Update Record' action and select a single-select dropdown custom field, you will now see the Standard and Dynamic toggle option for that field.
How agencies will use this
This update allows for more flexible data management within HighLevel workflows. For example, an agency might have a custom field for 'Client Tier' (e.g., Bronze, Silver, Gold) that is a single-select dropdown. Previously, if you wanted to update this field via an automation based on a client's spending, you'd struggle if the tier was calculated dynamically. Now, you can use a merge tag. If a contact fills out a form that includes a 'Desired Service Level' text field, you could then use a 'Create/Update Record' action to map that text field's value (e.g., {{contact.custom_fields.desired_service_level}}) directly into the 'Client Tier' picklist field, provided the values match. This automates the assignment of picklist values based on dynamic input, removing manual intervention or complex workaround steps.
Our take
This is a small, but necessary, quality-of-life fix. It addresses a specific limitation within the 'Create/Update Record' workflow action. It's not a major new feature, nor will it revolutionize your agency's operations overnight. However, for those who ran into this specific limitation when trying to build more sophisticated automations, it's a welcome improvement that simplifies certain workflow designs. For most, this will be a minor, almost unnoticeable, update.
Source: Official HighLevel announcement

