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

HubSpot should provide a way to customize category slugs so users have proper control over language switching. Alternatively, they should offer a mechanism—similar to language_variants('localized') for standard pages—that allows developers to retrieve localized category URLs for multilingual implementations. Because currently, implementing a language-switch to a KB is a hastle. ...その他を表示

Now that I am a Partner Admin to some of our clients, I realized that I am not able to do "high-risk" actions like CRM Manual Data Back Up and Knowledge Base Migration.  I checked with Support and these actions can be done only by a Super Admin.  I normally have to do this work for clients, now I have to request for a paid Super Admin seat to be able to do this. I believe the expectation is that a Super Admin is meant to action on more "high-risk" actions (like migrating the KB) since it's irreversible.   I think a good middle ground would be something like a Partner-requested, Admin-approved setup so there doesn't need to be a change or permissions. Tagging Product team cause I can see how this would make things a lot smoother. ...その他を表示

I am reaching out because we are currently facing a significant technical limitation that is preventing us from fully migrating our processes from Typeform to HubSpot. The Feature Needed: We need the ability to use Personalization Tokens (or dynamic placeholders) within the "Redirect to another page" URL setting of a HubSpot form. The Use Case: After a lead submits a form, we want to redirect them to a booking page (e.g., a calendar or a custom application) and pass their data (email, phone, etc.) via query strings so the next step is pre-filled. Example URL: https://www.example.com/booking?email={{contact.email}}&phone={{contact.mobilephone}} The Current Problem: Character Blocking: Currently, the "Redirect URL" field in the form editor blocks the use of brackets {{ }} or []. When we try to use HubSpot syntax, the system throws an error or saves it as plain text instead of rendering the variable. Missing "Piping" Functionality: In tools like Typeform, "Piping" (passing an answer from a previous step into a URL or following question) is a native feature. In HubSpot, this currently requires complex Custom Code workarounds or hidden redirect pages, which is not scalable for a marketing team. Why this is important: Without the ability to pass contact data dynamically through the redirect URL, the user experience is fractured, as leads have to enter their data twice. This is a "hard roadblock" for us and, I believe, for many other companies looking to consolidate their tech stack within HubSpot. Proposed Solution: Allow the use of standard HubSpot Personalization Tokens within the Form Redirect URL field, similar to how they work in HubSpot Emails or Landing Pages. Is there a planned update for this, or has anyone found a reliable way to bypass the character restriction without using heavy custom-coded middleware?   Best regards, Jan ...その他を表示

On Hubspot settings > Use defaults we do have option to set the font type and size. However this default doesnpt apply to Templates.   Perhaps having an option to set the default font type and size on the templates would save a lot of time especially when we are using message templates quiet often ...その他を表示

We want to be able to create a link for some deals in Draft stage but thats currently only possible if the quote is published. So we either: 1. Need to be able to create a quote link for specific quotes in draft stage through a workflow 2. Or be able to push certain quotes from Draft to Published which will create the link we need - again through a workflow.  The reason we need this is because some of our quotes in draft stage are ready to present to the customer so we want to sent them this sample link to preview, which is currently not posisble though a workflow.  ...その他を表示

What Hubspot could do instead would be open a dropdown where we can seletec the workflow you want to see the contact enrolled and select that checkbox(es) OR can simply move the option we currently have in the segment called "Workflow Enrollment" to the contact view filter as an option but cannot remove this option from there There is ctually a thread linked with it, but I haven't seen any sugestion of improvement, that's why I'm posting as a new idea Here is the thread ...その他を表示

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

I recently started using HubSpot for my company's social media. I do like a lot of the features, but it falls short in some areas. It is important to have the proper ratios that match the applications formatting. stories and reels are usually the 9:16 ratio and will look silly at the 4:5 ratio. People will be less likely to use Hubspot to upload stories and reels if there are these limitations.   Linkedin and Instagram allow up to at least 20 photos per post. HubSpot only allows 9. This should be updated as other posting website and applications allow for more than 9, if not all 20.   The locations for the post are amazing, but it does not specify the address. There are a lot of places with the same name, so I do not use this feature through HubSpot because I do not want to risk tagging the wrong location. ...その他を表示

Our global HubSpot account is used by teams operating in multiple countries and languages. To ensure strong user adoption, it is essential that we are able to translate custom properties—including custom pipelines and pipeline stage properties—into a broad range of languages. This need is particularly important for our Sales Representatives and might even become a roll-out roadblock.   Currently, HubSpot supports only a limited set of languages for custom translations: Chinese, Dutch, English, French, Finnish, German, Italian, Japanese, Polish, Portuguese, Spanish, and Swedish. To fully support our multilingual operations, we also require the ability to translate custom content into Slovenian (sl) and Slovak (sk). ...その他を表示