Great minds think alike

Currently, dealing with (hidden) fields in existing forms requires manually editing each form individually. This process becomes time-consuming and tedious, especially for organizations managing numerous forms with multiple (hidden) fields that change over time.   I'm especially thinking about hidden fields for language or utm-parameters:   Hidden fields typically used in multiple HubSpot forms   We recently decided to add another hidden field, so we had no other choice but open each form individually to do so.   It would be nice to have a feature that allows users to add (hidden) fields to multiple forms simultaneously. This functionality would significantly streamline form management, particularly for hidden fields whose placement within the form is not critical. Plus, it would reduce the potential for oversight when updating form structures. ...read more

The new Beta form doesn't allow the use of properties from custom objects, it would be wonderful to have that ability on the Legacy Form.  The lack of this ability causes unneeded properties to be created so we can then workflow the property to the Custom Object/Create the Record in the Custom Object. ...read more

We would like to enable the form setting: Pre-populate fields with known values   My idea: New ability per form field to turn off the prepopulation.   Our use case is: We would like all fields to prepopulate except for the "agree terms" and "subscribe to newsletter" fields, which should always be set to "no" on page load due to legal requiremetns. ...read more

We would like to be able to dynamically change the consent options shown to website visitors in a form depending on their country.  Different countries have very different data privacy and consent management requirements now, and it would be very useful to only gather the consent required for that region. The existing logic for dependent fields could be used, so then when a visitor selects a country from a field drop-down, a country-specific set of communication consent and privacy options show. It would be useful to still have a "default" set so that the HubSpot user doesn't have to create dependent consent options for every country in their drop-down field. ...read more

If you have a mandatory field on HS forms that has not been filled yet, the 'please complete this required field' warning appears as users click through the different fields, instead of popping up only as you attempt to submit. This is not good UX. Users normally would only want to know which mandatory field they have not yet filled upon clicking the CTA to submit the form, NOT as they move through the form. Currently you cannot customize the form field validation behavior directly in HubSpot's forms tool. The only change this behaviour is to do custom coding which can be expensive. It will be good to have this behaviour as a default on the forms instead of having to custom code. ...read more

We have followed official docs and successfully added an embedded HubSpot form into our application:  https://knowledge.hubspot.com/forms/how-can-i-share-a-hubspot-form-if-im-using-an-external-site   Our application can be installed in any AWS account with any domain chosen by the customer. In other words we don't control installations or domains.   After 16th May 2024 (as stated in the link provided) HubSpot started to treat any form submission as spam if the source is not added as a site domain. Since we don't even know what those domains could be we have no way to overcome this situation.   After talking with HubSpot support apparently there is "no way to adjust this process". I really think you should allow this behavior since it was the way your platform was working before the change.   I would really love to have a way to configure a form to be public and completed by anyone despite its domain source. In this case the form is for sending newsletters to customers or any person interested in them (we allow to any annonymus person to complete this form from our public website or from their custom installation). ...read more

I would like to pre-fill the form fields with known data. Not only when a visitor is returning on the same device, but like the dynamic fields you can use in emails or website text. ...read more

Overall, the new form editor with enhanced conditional logic is a VAST improvement with tons of promise, two big drawbacks in current beta state that are preventing us from actually testing in a client-facing capacity though -   Hidden Fields: Currently, you cannot use hidden fields in the same way that you can with the legacy forms editor. You can hide fields when certain conditions are met, but in the old from, it was really helpful to be able to use hidden fields to pass values along to contacts/companies/tickets upon submission. Theoretically this is still possible with workflows (contact has submitted "x" form, populate with "y" values), but there's a lot of reasons why it would be better to accomplish this natively in the form as opposed to through workflow. Both because of maintenance/number of workflows, and to keep a stronger hold on permissions around workflows in general.   Non-contact/company properties: Currently, this is the big blocker in allowing us to actually test this beta with a public-facing form in the new editor. The new logic is a VAST improvement over what we had previously, but we're primarily trying to create tickets based on form submissions to take advantage of this logic. In current state, the only way we could do that is creating a bunch of contact properties that we don't have much use for and syncing them over to a ticket. Ideally, we'd be able to ask for ticket properties in the form editor same as we can in the legacy editor. Sync fields (with their various limits) is not a good solution here either, because we'd still be creating contact properties that have no use other than to be a container to sync over to a ticket, which is not ideal.    ...read more

Hi!  We recently started to test out the beta multi-step forms.  This tool is great but lacks the ability to have hidden fields.  We need to capture data in hidden fields and really need these feature before we can start implementing these forms on our pages.  Hope this can be added soon! ...read more