Dynamic Value Chips Get Three States for Better Error Segmentation

TL;DR

Dynamic value chips now have three distinct colors (blue, yellow, red) to show value status more clearly. This is a minor quality-of-life update; no immediate action is needed from agency owners.

Who this affects

This update affects all HighLevel agency owners and SaaS entrepreneurs who use Automations. HighLevel has not confirmed specific plan levels or sub-account setups that might be exempt or uniquely affected, so assume it's a general change for all users interacting with workflows.

What changed

Dynamic value chips have been improved to provide better error segmentation. Key changes include:

• Chips now display in three states: blue, yellow, or red, moving beyond the previous two-state system.
• A new yellow chip state indicates a value exists on the platform but is not sourced by the current workflow.
• The blue chip state confirms a value is available within the current workflow.
• The red chip state signifies that a value does not exist on the HighLevel platform.
• Spacing inside handlebars no longer impacts dynamic value recognition. For example, {{ attribution.first.url }} and {{attribution.first.url}} are both now recognized correctly. HighLevel has not confirmed any limits, plan gating, or specific rollout status for this update.

Where to find it

This update is found within HighLevel's Automations section. Specifically, it impacts how dynamic value chips display when configuring workflow actions or conditions that use custom values, contact fields, or other dynamic data points. HighLevel has not published a more precise navigation path.

How agencies will use this

Agencies will use this by quickly identifying issues in their automation workflows. For instance, if an agency builds a workflow to send an SMS with a contact's {{ contact.custom_fields.last_purchase_date }} and the chip is red, they'll know that custom field doesn't exist for the contact or on the account. If it's yellow, they'll understand the field exists on the platform, but the current workflow isn't supplying that specific value, perhaps because it's triggering from a form submission that doesn't capture it. This allows for faster debugging and ensures that dynamic values resolve correctly in communications or internal processes.

Our take

This is a minor quality-of-life update. While useful for debugging workflows, it doesn't introduce new capabilities or significantly change how agencies operate. It's an incremental improvement for workflow builders, but not one that demands immediate attention this week.