What changed

Dynamic value chips now support three states instead of two. This makes it easier to tell the difference between a value that exists but is not available in the current workflow, and a value that is actually invalid.

How it works

Each chip will appear in one of these states:

• Blue: The value is available in this workflow. It can be filled from the contact record, a system value (like the current date), or a previous step.
• Yellow: The value exists, but it is not available in this workflow. For example, a Google Sheets value in a workflow that has no Google Sheets step. In this case the chip renders blank unless another workflow passes the value in through an “Add to Workflow” action with input parameters.
• Red: The value does not exist. Nothing on the platform matches it, so it will not render in any workflow.

Spacing inside handlebars is now handled more consistently as well. For example, values like null and null are treated the same.

Why this matters

Previously, any value that did not render could appear as an error, even when the setup was intentional (such as passing values between workflows). With the new split states, red is reserved for truly invalid values, and yellow indicates a valid value that just is not sourced in the current workflow.