This idea is primarily for developers, technical admins, and advanced HubSpot users who regularly work with the CRM APIs, custom code actions, integrations, or external systems. Problem: Today, the only way to see a property’s internal name is to click into each individual property. When you’re working with APIs or external tools, internal names are what actually matter — not labels. If you need to reference or validate many properties at once, this becomes extremely time-consuming and disruptive. You’re forced into a repetitive loop of opening properties one by one just to copy a single value. Proposed Improvement: Add Internal Name as an optional, visible column in the Properties table (similar to how names, groups, and access types are shown). Ideally, this column would also be searchable and sortable. Why This Matters: Dramatically improves developer and admin efficiency Reduces friction when building integrations, workflows, and custom code Makes property audits and troubleshooting far easier Aligns the UI with how properties are actually used in APIs and automation This small UI enhancement would save significant time for anyone working at scale with HubSpot data and would meaningfully improve the developer experience across the platform.
... Afficher plus