What's new?

Dynamic value chips have three states now instead of two. A chip used to be recognized or not recognized, so anything the builder couldn't resolve came back red with "value not recognized". The new middle state is a yellow chip, and it covers values that are real on the platform but have no source in the workflow you have open.

How it works

Every chip lands in one of three states:

• Blue, value available in this workflow. The workflow can fill it, whether that comes from the contact record, a system value like the current date, or an earlier step.
• Yellow, value not available in this workflow. The value is real on the platform, but nothing in this workflow supplies it, for example in a workflow with no Google Sheets step. It renders blank unless another workflow passes it in through Add to Workflow with pass input trigger parameters.
• Red, value doesn't exist on the platform. Nothing on the platform matches it, for example , so no workflow will render it.

Spacing inside the handlebars stopped mattering too. The platform stores Attribution Url as {{ attribution.first.url }} with the spaces, so typing used to come back red. Both forms match now.

Why we built it

Earlier all fields which wouldn't render would show an error state with a red chip. However you might drop into an Add Notes action on a workflow that no invoice trigger starts, or hand a value from one workflow to another through Add to Workflow.

The red chip earlier called those values unrecognized and pointed you at the picker, so a configuration you built on purpose read like a mistake you had made. Splitting the states puts red back on the cases worth acting on. Red now means the value is wrong. Yellow means check whether something else supplies it.

Preview