Great minds think alike

When externally embedding HubSpot forms there is an option to "Set as raw html" to allow the form to inherit your website's css and not use the form builder styles.    HubSpot CMS forms always inherit their theme's styles and there is no option to use the HubSpot form builder styles.  So using a form on the HubSpot CMS currently provides less functionality than using a HubSpot form on an external site.    There should be an option to set your form module to inherit HubSpot form builder styles.  ...read more

With various AI platforms continuing to gain momentum, it would be super beneficial to have the ability to parse out leads from ChatGPT, Claude, Perplexity, etc. from into their own, new Original Source category: AI Search.   This way, HubSpot CRM users can more easily see data in their dashboards at a high level and can pinpoint which popular AI platforms are producing leads. This is especially important since, currently, the Original Source they get lumped into just covers any website that isn't their own (outside of search engines).   This new option allows marketers to make more informed decisions on their strategies and what channels to pay attention to more. ...read more

We have set up deal pipeline rules to prevent users from altering closed deals. However, we cannot prevent users from altering existing line items of that deal after it was closed. This way, the deal amount - a crucial property - can be altered.    I suggest deal pipeline rules to extend to line items (or any comparable solution) so we can REALLY prevent users from altering closed deals. ...read more

Currently when we add any existing properties as a dashboard quick filters, the only available operators are  "contains any of, Is Known, Is Unknown and Doesnt contain any of" Its missing "has ever been equal to, has ever contained" This is crucial to track historical data! ...read more

Per this thread, I am requesting that you provide us a setting to turn off this feature. It would be ideal if we could turn this off at either at the individual user level or at the admin level. This autosave feature is extremely disruptive to our workflow. ...read more

Currently, you can open an IFrame modal within the UI Extensions actions (https://developers.hubspot.com/docs/guides/crm/ui-extensions/sdk#open-an-iframe-in-a-modal).  However, you cannot close it without manually clicking the close "X" in the modal. This creates an extremely bad user experience for the case of opening forms within an iframe.  Now a user needs to: 1. Open the form (iframe modal) 2. Fill out the information 3. Submit the information 4. Then go and close the iframe manually (it should just close automatically in the last step) Some easy solutions to this could be to simply allow an iframe to be embedded within a react component (rather than as an overlay), then you are masking what is an internal/external resource - in this case you should be able to expose a panel of buttons to programatically close the iframe as you can any other overlay.  This solution would allow you to collapse steps 3 and 4 above by skipping step 3 and ensuring progressive updates in the iframed forms in step 2, and just providing a single "Submit" button.  Either way, even for static content, it's opening and closing can be controlled without leaving the 'hubspot' sandboxed react experience. Another solution would be to add a listener to the iframe, and allow the child window to communicate with that listener using some predefined set of commands.  This is probably more challenging, but would open up the possibilities for devs even more. ...read more

Hi Community! I am posting this idea on behalf of a customer, please vote for it!    When we use date properties in the CRM > objects columns (contact, companies, etc.) we get the values in the following format: January 1, 2025, instead of 01/01/2025.   However, when we access the property from the "see all properties", we see the value as following: 01/01/2025.   The request here is being able to choose the format displayed in CRM> Contacts/Companies, etc., based on our preferences.   Please vote for this idea for visibility. Thanks!   Mélani --- ¡Hola, comunidad! Publico esta idea por mi cliente, por favor, ¡votad por ella!   Cuando decidimos mostrar las propiedades de fecha en las columnas de propiedades del CRM (contacto, empresas, etc.) nos aparecen los valores en el siguiente formato: 1 de enero de 2025, en lugar de 01/01/2025.   Sin embargo, cuando accedemos a la propiedad desde la vista de todas las propiedades, vemos el valor como: 01/01/2025.   La solicitud aquí se basa en que se pueda elegir el formato que se muestra en CRM> Contactos/Empresas, etc., dependiendo de nuestras preferencias.   Votad por favor para darle visibilidad a la idea. ¡Gracias!   Mélani ...read more

Description: Currently, HubSpot’s dropdown fields only support a flat structure, which makes it challenging to organize and select options that naturally belong in a hierarchy (e.g., Category > Subcategory > Detail).  I’d like to suggest that HubSpot introduce tiered or hierarchical dropdown menus. For example: Selecting “A” could reveal sub-options like “AA,” which in turn could reveal further sub-options like “AAA.” This structure would make it easier for users to navigate complex option sets without cluttering the dropdown with too many items at the same level. A Level 1 └── AA Level 2 └── AAA Level 3   Use Cases: Classifying companies or deals with multi-level categories. Organizing product or service options by main category and subcategory. Streamlining forms and reducing user error by showing only relevant sub-options based on previous selections. Benefits: Enhanced user experience, especially for large datasets. Improved data quality through more intuitive field structures. More flexible customization for businesses with complex workflows. Possible Implementation Ideas: Allow admins to define parent-child relationships between dropdown options. Let users expand/collapse dropdowns to navigate tiers. Offer conditional dropdown logic within a single dropdown property, rather than relying on separate fields and conditional visibility. Thanks for considering this enhancement — it would be a game-changer for us and most likely other companies that rely on structured data collection in HubSpot! 🚀 ...read more

Hi HubSpot team,   We are currently doing integration between HubSpot to a 3rd party app and need to align Internal Values in Persona Property to be the same values in this 3rd party app (both HubSpot & 3rd party's internal values need to be the same).    We noticed that the Persona property is set by HubSpot as default.    Hence, we'd like to ask if you could add this feature or your developers could assist with changing the Internal Value in Persona Property.   Also welcome other alternative options.   Thank you.   Kind Regards, Victor       ...read more