Hi HighLevel Team,

I’m currently building production templates using Custom Objects and Object-Based Workflows (Beta) and have run into a limitation that affects real-world usability.

Current behavior:

In object-based workflows (e.g. Enrollment-based workflows), the custom variable picker only exposes fields on the triggering object. Fields from associated custom objects (e.g. Student, Program) are not available in the variable picker, even though the associations are properly configured and usable elsewhere in the UI.

Impact:

This prevents common, expected use cases such as:

Auto-naming records using associated object fields (e.g. Student Name – Program Name)

Building dynamic notifications that reference related object data

Creating clean, automated workflows without brittle workarounds or manual steps

Requested enhancement:

Expose associated custom object fields in the workflow variable picker for object-based workflows, similar to how related Contact / Opportunity fields are accessible in legacy workflows.

Ideally:

Associated objects appear in the variable picker

Fields are scoped to valid associations

This would significantly improve adoption of Custom Objects and allow builders to ship cleaner, safer automation without relying on manual naming or external systems.