Great minds think alike

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

Who is this feature for? This feature is for marketers, designers, and anyone using HubSpot's new form editor to create and manage forms on their website. It would particularly benefit those without coding knowledge who want more control over form design. What is their goal? The goal is to provide users with an easy way to align buttons (such as "Get in Touch" or "Submit") within forms without needing to switch back to the legacy editor or manually edit HTML/CSS code. What value will this add? Adding button alignment options (left, center, right) directly within the form editor’s styling options will improve the user experience by allowing for quicker design adjustments. It will reduce the reliance on legacy tools or custom code, streamlining the form creation process and keeping everything in the modern editor.  Are there examples of other places or products that have this feature? The legacy HubSpot form editor already has this feature. It would make sense to bring this functionality into the new editor to maintain and improve usability. ...read more

I would like the option to manually enrol a ticket from the records page into the workflow. ...read more

I would love to be able to add in the new association labels using a workflow - rather than needing to do this manually. this would enable businesses who have contact A who makes a booking and Contacts B, C, D etc who attend a course or an event flagged as attendees. so a business knows which are valuable contacts.   It would also be helpful to be able to use a workflow to send different communications to clients based on their association tag. ...read more

The new property sync property types have been tremendously helpful, but would be great if we can increase the limit from 25.  Very convenient to avoid working through associations, then searching dependent objects....hopefully this limit gets increased! ...read more

We use Hubspot forms frequently for our internal teams to create Hubspot tickets. It'd be beneficial to have the new form editor connect to tickets so that we can take advantage of the additional flexibility with conditional logic to create tickets. Thanks! ...read more

It would be great if HubSpot had a calendar for Marketing which showed all content going out - currently there are separate ones for Social, Email, and Campaigns. Please can one be made that combines all of the above calendars?  ...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

Currently we cannot select or reference meeting attendees in reporting. This would be a very important feature for reporting on sales activities.   As several salespeople can attend the same meeting, we're currently unable to accurately report on their customer interactions. ...read more