Great minds think alike

Currently, ACH payments are only available to be received in HubSpot payments by US HubSpot accounts.  Stripe supports ACH payments to be received by companies outside the US.  It would be helpful if HubSpot is able to match this ability.   ...read more

We have a workflow that updates an external system, when properties change on Companies or Contacts.  To have this workflow run whenever a property changes, we have to have a filter group in the Workflow for every property we want to manage.  This is a very big list, we have over 25 Company properties we need to track changes on, so my workflow has to have 25 OR conditions.  This is extremely hard to manage long term, and not to mention someone can accidentlally delete those conditiions very easily.   In Salesforce you can have a Flow run everytime a record changes.  No matter what property changed.  This would be extremely useful.  This a huge gap in functionality.   This workflow also needs to run everytime the record changes, so it needs to support Reenrollment.  ...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

I noticed that the recent update changed the comment color to a pale yellow, which blends in too closely with the white background, making it difficult to read. I would appreciate the option to revert to a brighter color or to select a color that I prefer. ...read more

Being able to surface data from one object on another object without the use of workflows has been a huge improvement.    However, now that the data can be visualized on the second object, our users often times need to be able to update it while on that object without leaving the object's workscreen.    For example, we are syncing some key Company properties to the Lead Object so that data about the company stays evergreen but our sales teams can see that data in the leads tool while working their leads. It would be great if, as they engage with the lead, they had an easy way to update these values without having to leave the sales workspace. Currently it leads to some confusion when a property can not be edited due to it being a sync property - and even having a prompt that opens the appropriate Company property or something that tells them that the field needs to be updated on the Company object would be very useful in making sure data gets updated.    Ideally we'd be able to set sync rules the same way we do with other tools (such as data sync for integrations) but even just allowing for data to be updated in either object would help immensly!  ...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

It would be really helpful to be able to search for a Hubspot Company ID or Contact ID (or other ID, like Products or Services) directly in the Hubspot search bar. Seems like this search bar looks at everything except ID numbers, which would be a simple thing to include and help us.    We include Hubspot IDs to track the results of some marketing campaigns, associating them with certain URLs, etc. to determine the company that likely clicked, etc. ...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

It would greatly improve our WhatsApp integration if HubSpot could automatically capture any user-initiated WhatsApp message—whether from the embedded chat widget or direct WhatsApp app—and: Auto-upsert contacts by phone number when a new user messages for the first time. Log inbound messages on the contact’s timeline and surface them in the Conversations inbox without manual copy-paste. Trigger workflows (opt-in, welcome series, unsubscribe handling, qualification flows, etc.) based on the inbound message or detected keywords. Allow chatflows to ask for custom fields (name, email, phone) directly in-chat, mapping replies back to HubSpot contact properties as part of the chatflow builder (no external middleware required). Use Case: We’ve connected our WhatsApp Business number and can send approved HSM templates outbound via workflows, but we cannot yet: Automatically create a new contact when an unrecognized number messages us. Sync their replies into HubSpot without manual record edits. Drive post-reply logic in chatflows based on those messages or property updates. Adding first-class support for inbound message capture, contact upsert, and chatflow-driven data collection would close the loop on the entire WhatsApp customer journey, reduce manual work, and let us build fully conversational lead-capture forms inside WhatsApp. Benefit to HubSpot Community: Many customers use WhatsApp as a primary support and sales channel. Native inbound sync and chatflow data collection would: Eliminate middleware complexity. Surface customer conversations in HubSpot automatically. Unlock powerful workflow triggers on live inbound messages. Reduce friction when building multi-step conversational forms. Please let me know if there’s any additional context I can share—and thanks for considering this enhancement! ...read more