What’s new?

We’ve upgraded the field picker in both the Custom Value Picker and If/Else action. Search now returns fields from inside nested folders, navigation across folders and subfolders is easier, and the field list is better organized for a cleaner, more consistent selection experience.

Improvements

• Nested field search – Find fields inside folders and subfolders without opening each one first.
• Easier navigation – Move through nested folders more smoothly.
• Cleaner organization – Fields are grouped more clearly, making them easier to scan.
• Better readability – Long field names now show tooltips, making it easier to read full values without cluttering the picker.
• Consistent experience – The picker now feels the same across If/Else and Custom Value Picker options across the platform

How it works

When you search for a field, matching results can now appear even if that field lives inside a folder or subfolder. The picker also uses a more consistent dropdown pattern across workflows, so finding and selecting fields feels the same in Custom Values and If/Else.

How to use it

• Open the field picker in Custom Values or an If/Else branch filter.
• Type the field name in search.
• Select the matching field directly from the results, including fields stored inside nested folders.

Why we built it

Previously, finding the right fields in automations took more effort than it should have. Users had to manually open folders and return to the search box to find nested fields, which slowed setup and made some available fields easy to overlook.

Additional Notes

• Search now shows matching field names from inside folders and subfolders.
• Only enabled folders appear in search results. Once you clear the required dependencies, the available fields would show up.
• The updated picker experience is aligned across If/Else and Custom Value Picker.
• Users will only see fields and folders that are available and enabled in that context.

Preview

What’s new?

We’ve upgraded the field picker in both the Custom Value Picker and If/Else action. Search now returns fields from inside nested folders, navigation across folders and subfolders is easier, and the field list is better organized for a cleaner, more consistent selection experience.

Improvements

• Nested field search – Find fields inside folders and subfolders without opening each one first.
• Easier navigation – Move through nested folders more smoothly.
• Cleaner organization – Fields are grouped more clearly, making them easier to scan.
• Better readability – Long field names now show tooltips, making it easier to read full values without cluttering the picker.
• Consistent experience – The picker now feels the same across If/Else and Custom Value Picker options across the platform

How it works

When you search for a field, matching results can now appear even if that field lives inside a folder or subfolder. The picker also uses a more consistent dropdown pattern across workflows, so finding and selecting fields feels the same in Custom Values and If/Else.

How to use it

• Open the field picker in Custom Values or an If/Else branch filter.
• Type the field name in search.
• Select the matching field directly from the results, including fields stored inside nested folders.

Why we built it

Previously, finding the right fields in automations took more effort than it should have. Users had to manually open folders and return to the search box to find nested fields, which slowed setup and made some available fields easy to overlook.

Additional Notes

• Search now shows matching field names from inside folders and subfolders.
• Only enabled folders appear in search results. Once you clear the required dependencies, the available fields would show up.
• The updated picker experience is aligned across If/Else and Custom Value Picker.
• Users will only see fields and folders that are available and enabled in that context.

Preview

We've added two in context safeguards to the Contact Tag trigger to prevent the most common configuration mistakes and protect users from unexpected workflow behavior.

What's New

Retroactive Enrollment Info Banner

When a tag is added to the Contact Tag trigger, a subtle info banner now surfaces to clarify that the trigger only applies to tags added after the workflow is published. The banner links directly to the retroactive enrollment guide, where users can follow the steps to bulk import existing tagged contacts into the workflow.

No Filters Warning

If a user attempts to save the Contact Tag trigger without configuring any filters, a warning now surfaces explaining that the workflow will trigger for every tag added or removed across all Contacts, which may cause unexpected behavior. The warning offers two clear paths forward:

• Add Filter (primary CTA) — returns the user to filter configuration
• Save without filters — preserves the option for advanced use cases

How It Works

Retroactive Enrollment Info Banner

• Appears when a tag is added inside the Contact Tag trigger filters
• Includes a link to the retroactive enrollment support article
• Dismissible via the close icon. Once dismissed, it will not appear again for that user
• If not dismissed, it follows a frequency cap of 3, after which it stops appearing automatically

No Filters Warning

• Triggered when the user attempts to save the Contact Tag trigger with zero filters configured
• The Add Filter CTA returns the user to filter configuration
• The Save without filters CTA preserves the option for advanced use cases

Why This Matters

• Reduces confusion around post-publish trigger behavior by setting clear expectations upfront
• Prevents accidental workflow runs across the entire contact base
• Surfaces the retroactive enrollment path right where users need it, instead of leaving it buried in documentation
• Keeps power users unblocked by making every guardrail dismissible or overrideable

We've added two in context safeguards to the Contact Tag trigger to prevent the most common configuration mistakes and protect users from unexpected workflow behavior.

What's New

Retroactive Enrollment Info Banner

When a tag is added to the Contact Tag trigger, a subtle info banner now surfaces to clarify that the trigger only applies to tags added after the workflow is published. The banner links directly to the retroactive enrollment guide, where users can follow the steps to bulk import existing tagged contacts into the workflow.

No Filters Warning

If a user attempts to save the Contact Tag trigger without configuring any filters, a warning now surfaces explaining that the workflow will trigger for every tag added or removed across all Contacts, which may cause unexpected behavior. The warning offers two clear paths forward:

• Add Filter (primary CTA) — returns the user to filter configuration
• Save without filters — preserves the option for advanced use cases

How It Works

Retroactive Enrollment Info Banner

• Appears when a tag is added inside the Contact Tag trigger filters
• Includes a link to the retroactive enrollment support article
• Dismissible via the close icon. Once dismissed, it will not appear again for that user
• If not dismissed, it follows a frequency cap of 3, after which it stops appearing automatically

No Filters Warning

• Triggered when the user attempts to save the Contact Tag trigger with zero filters configured
• The Add Filter CTA returns the user to filter configuration
• The Save without filters CTA preserves the option for advanced use cases

Why This Matters

• Reduces confusion around post-publish trigger behavior by setting clear expectations upfront
• Prevents accidental workflow runs across the entire contact base
• Surfaces the retroactive enrollment path right where users need it, instead of leaving it buried in documentation
• Keeps power users unblocked by making every guardrail dismissible or overrideable

We've added two in context safeguards to the Contact Tag trigger to prevent the most common configuration mistakes and protect users from unexpected workflow behavior.

What's New

Retroactive Enrollment Info Banner

When a tag is added to the Contact Tag trigger, a subtle info banner now surfaces to clarify that the trigger only applies to tags added after the workflow is published. The banner links directly to the retroactive enrollment guide, where users can follow the steps to bulk import existing tagged contacts into the workflow.

No Filters Warning

If a user attempts to save the Contact Tag trigger without configuring any filters, a warning now surfaces explaining that the workflow will trigger for every tag added or removed across all Contacts, which may cause unexpected behavior. The warning offers two clear paths forward:

• Add Filter (primary CTA) — returns the user to filter configuration
• Save without filters — preserves the option for advanced use cases

How It Works

Retroactive Enrollment Info Banner

• Appears when a tag is added inside the Contact Tag trigger filters
• Includes a link to the retroactive enrollment support article
• Dismissible via the close icon. Once dismissed, it will not appear again for that user
• If not dismissed, it follows a frequency cap of 3, after which it stops appearing automatically

No Filters Warning

• Triggered when the user attempts to save the Contact Tag trigger with zero filters configured
• The Add Filter CTA returns the user to filter configuration
• The Save without filters CTA preserves the option for advanced use cases

Why This Matters

• Reduces confusion around post-publish trigger behavior by setting clear expectations upfront
• Prevents accidental workflow runs across the entire contact base
• Surfaces the retroactive enrollment path right where users need it, instead of leaving it buried in documentation
• Keeps power users unblocked by making every guardrail dismissible or overrideable