クリエイティブな才能を開花させよう

HubSpot allows you to create custom properties to organize assets such as marketing emails, marketing events, and workflows. For example, here is a custom property that groups marketing events by the product that the event is about.   Marketing Events list with the custom Product multi-select property.   Unfortunately, these properties are not available to be used anywhere in HubSpot. They are only available on the page listing those records as an additional column and filter. Here are some places you might want to use these properites that you can't: Lead Score. You can't filter marketing events or marketing emails or workflow enrolments by a custom property. (e.g. score any email with interaction = high as 2 points and emails interaction = low as 1 point based on a custom interaction level property.) Workflows. You can't take workflow actions based on custom properties. (e.g. unenroll if enrolled in workflow with Type = followup based on a custom Type property.) Segments. You can't filter records in segments based on these properties. (e.g. Attended a Marketng Event for the "Facilities" product based on the custom Product property.) These properties are very interesting because they are visible and accessible to the user and are pitched as a great way to organize assets. Unfortunately, we can't access that organization anywhere except the asset's page, so it's usefulnessis severely limited. ...その他を表示

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. ...その他を表示

Add a configurable watermark option when setting up a File Upload property in HubSpot. The watermark setting can be enabled or disabled directly at the property level. Problem it solves Files uploaded through forms may contain sensitive or confidential information. Allowing watermark configuration at the file upload property level helps reduce the risk of misuse or unintended disclosure, while giving teams control based on different data sensitivity needs.   ...その他を表示

We need the ability to append custom single-line and multi-line text values when merging records or in a workflow (where the "append" option is missing).   As an agency, we use the a custom text property to house Partner IDs for our brands inside different PRMs, but we often run into the case where major publishers, such as SoftwareAdvice, have multiple IDs; since we use it as a unique identifier, this creates duplicates that, when merged, remove the alternative IDs that we need to see.   Our publishers sometimes have dozens of Parner IDs that we need to keep track of and see inside of one company record. Reviewing the property history and manually adding them just isn't feasible.   Currently, the only solution is to download our duplicate companies every week or two and append the values in a spreadsheet, then import them back into the system and proceed to merge the duplicate records.   Neither of these "solutions" are what you'd expect from a professional CRM like HubSpot, and we need a better way.   It would also be nice if there was a possibility to retrive and append values from a properties history in a workflow as well. ...その他を表示

Currently, we cannot easily use reporting and Workflows for manually sent 1-to-1 emails since emails sent via Sequences are technically 1-to-1 emails and there is no way to separate the two easily.   It would be great if there were some property that we could filter on to separate the Sequence emails and manual 1-to-1 emails.    We use sequences for our automated marketing emails. Our sales reps have quotas for manually sending 1-to-1 emails and some deal stages require manually sending custom 1-to-1 email. ...その他を表示

In filter views, the owner column used to only show the name. Now it shows the user name and email. This makes this column wide, or cutoff and sloppy looking. It's additional noise not needed. For the HS concern of clarifying when there are a duplicate users, put the email in the dropdown choice filter, but once shown on screen provide an option in the property settings to only show the actual user name.  ...その他を表示

Some of my customers wish that their CRM Users see fields that are created as "single Checkbox" as a "Checkbox" field (to check/uncheck) in the left column on object level (and other places). I am very surprised that this is only possible in forms. Why can't I change the visualization from "dropdown" to a "Checkbox"? ...その他を表示

Hello,   We are looking to adapt our chatflow for multiple languages across the globe. We currently have 3 "Select Industry" pick lists; one for each of our two business units and one that pulls in all industries.    That being said, we have loaded translations for these options, however the chatflow tool does not support the translated values. This is very frustrating and the only option that was given was to create a seperate property for that specific language. We are looking to deploy this across at least 6 different languages, which would require us to build no less than 12 different properties to satisfy the language varients, not to mention workflows to copy these to the English values that we use internally.    It would be great if translations are able to be surfaced in chatflows. We are not interested in a workaround as it is too cumbersome for our needs and will require ongoing maintenance. Can you please build functionality to support translated properties in chatflows? ...その他を表示

Currently when you close a deal the Amount in Company Currency property stops updating, so if you move a deal to closed won and the exchange rate is updated the next day, the conversion to company currency on that deal doesn't update which means your reporting is incorrect.   This is a big challenge for any business who needs to reporting acorss currencies.  ...その他を表示