C
Christopher Harris
You recently shipped "Use associated Company fields in the Custom Value Picker across the platform" — Company fields (standard + custom) are now selectable as custom values in Workflows, Emails, Contracts, Conversations, and AI, and each one resolves to the Company associated with the Contact at runtime.
Please extend that exact mechanism to Custom Objects.
THE GAP TODAY
In a contact-based workflow, the Custom Value Picker exposes Contact fields and (now) associated Company fields — but NOT fields from a Custom Object record associated with the contact. We can Create / Update / Clear an associated custom object record, but we can't read its field values back into the workflow. The data is stored but unusable in messages, conditions, notifications, and downstream actions.
WHAT I'M ASKING FOR
  • Add a Custom Object group to the Custom Value Picker, selectable by association label.
  • Each value resolves to the custom object record associated with the enrolled contact at runtime — identical to how Company resolves today.
  • Expose both standard and custom fields of that record.
  • Handle one-to-many: let me choose the association label and which record to pull (e.g., most recently created/updated, or first) — the same way record limits already work on associations.
  • Available on the same surfaces as Company: Workflows (If/Else conditions, messages, internal notifications, and action inputs), Email Builder, Conversations, Documents & Contracts, Bulk Actions, and Conversation AI.
USE CASES
  • A "Project" / "Policy" / "Order" custom object is associated with the contact — reference its fields (status, dates, amounts, IDs) directly in emails, SMS, and internal team notifications.
  • Branch a workflow on a custom object field (e.g., only send when the associated record's status = "Active").
  • Auto-fill contracts and proposals with associated custom object context, exactly like Company fields now do.
WHY IT MATTERS
The picker and the runtime resolution already exist — you built them for Company. Extending them to Custom Objects turns custom objects from a storage feature into something automations can actually act on, without webhooks or external tools as a workaround.