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

We really like using HubSpot's message templates, especially because of the feature that allows you to insert personalisation tokens, which are then automatically filled in the email.   Unfortunately, there is one essential feature that is available when saving Outlook templates but is still missing from HubSpot's message templates: it would be nice if you could store fixed recipient email addresses for specific message templates.   Specifically, from our point of view: we work with partners whose products we resell. When one of our customers orders a partner product, we have to send an email to our partner specifying which customer ordered which product with which key data. The partner requires us to always send this information to specific email addresses. And it would of course be easier for us if these email addresses were always stored with the message templates. ...その他を表示

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

Please implement support for Subresource integrity validation (https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) Reason 1 to implement this security measure: When a resource is referenced on the HTML code with a different domain from which the same HTML was loaded, then a malicious actor could interfere in the DNS resolution on the end user's machine, to make the resource be downloaded from a different location. Thus, a resource referenced with "https://js.hs-scripts.com/***.js" could be downloaded from a malicious server with malicious code. This type of attack can be prevented if HubSpot adds a verification string that allows the browser to confirm that the received asset is the expected one, without alterations. Reason 2 to implement this security measure: Even if there is no attack from a malicious actor. Security audits rise this security flaw as a vulnerability, causing reputational damage to the people maintaning the website and to the website's owner. Please provide a solution to this. ...その他を表示

Current Behavior: The {{ brand_settings }} HubL context variable provides access to branding assets (such as logos, color schemes, and domains) but is currently scoped exclusively to the portal’s primary (top-level) Brand Kit.   Use Case: Portals configured with multiple Business Units each maintain distinct Brand Kits. However, there is no programmatic way via HubL, CMS modules, or HubSpot APIs—to access the Brand Kits of these secondary Business Units.   Request: Extend the {{ brand_settings }} variable to allow developers to programmatically retrieve branding assets for any Business Unit Brand Kit within the same portal.   This would enable dynamic theming and asset management in multi-brand environments without requiring manual workarounds.   Benefits: Simplifies development for portals using HubSpot Business Units by exposing brand assets for all units natively in HubL templates and modules. Enables more flexible, scalable multi-brand CMS and email template designs. Eliminates reliance on external asset management or custom property workarounds. ...その他を表示

In the Government space, especially Department of Defense, clickable links for documents are frequently not allowed by their networks. I would like the ability to add attachments to templates, and have them carry over into sequences. This would greatly increase my ability to streamline communication and automate 60% of what I do into templates and sequences. ...その他を表示

Currently snippets can only be created manually and there is no way to create snippets in bulk such as through an import. It requires a lot of copy and paste which most users do have the time or resources to devote to.   It would be beneficial to have the ability to mass import snippets in HubSpot, given their versatility across different areas such as contact, company, deal, and ticket records, as well as in email templates, chat conversations, and when logging activities or notes. This feature would be particularly valuable if users could access it on both desktop and mobile platforms with a select multiple option. ...その他を表示

When we send an email template from a service record, and the email template has personalization tokens calling on other object records such as deal properties, the personalization token calls on the most recently made deal for the associated company to the service, even if another older deal (associated to the same company) is associated to the service record. This is counterintuitive. Why would the personalization token call on a deal not associated to the service record, when there is another deal already associated to the service record?  The default should be changed to call on the properties of the primary object association label, which is logical. I imagine many people don't realize this and are using email templates sent from service records that call on incorrect property values.    For example, I am sending an email from a service record. The service record is associated to ABC Company and the 2025 deal for ABC company. Both ABC Company and the 2025 deal are marked primary to the service record. Unrelated to the 2025 deal, ABC Company also has a 2026 deal that the sales team is working to close. When using an email template with personalization tokens in the service record, the personalization tokens call on the 2026 deal, not the 2025 deal. How would someone in the service record, that is associated to the 2025 deal, know the email template personalization tokens are calling on the 2026 deal, which they might not know about or have access to?    It was already suggested that we send the email from the deal instead of the service record, which we can't  do that. It has to be sent from the service record... otherwise the email won't automatically associate to the correct service record and we can't rely on someone remembering to go back and associate the service record to the email sent from the deal. We also can't turn on automatic logging of email activity from the deal to the service records since workflows are triggered based on email activity from within the service records, and the automatic association labeling is clunky and doesn't have a way of narrowing down to the right service record.  ...その他を表示

Hi HubSpot Community,   I'm writing to share some thoughts and suggestions regarding the new Case Study Beta feature. While it's a fantastic step forward, there are a few areas where I believe it could be further improved to provide users with even more flexibility and customization options.   Current Limitations:   Limited Listing Page Customization: The current listing page customization options, particularly around tag filtering, feel somewhat restrictive. Being able to create more granular filters and sorting options would significantly enhance the user experience and meet more business needs.   Lack of Child Theme: The inability to create a child theme specifically for case studies limits our ability to fully align the design with the rest of our website.    No Multilingual Variations: As with HubSpot's blog feature, the ability to create multilingual variations of case studies would be invaluable for global businesses.   Header and Footer Customization: While there are some options for customizing the header and footer, they are quite limited. This often leads to design inconsistencies across the website, as the header and footer don't match the overall site design.  Proposed Enhancements: Expand Listing Page Customization: Allow for more granular tag filtering and sorting options. (e.g., filter by solution and case study type; sort by date, popularity or custom field) Provide additional layout options for the listing page. (e.g., grid view or card view) Introduce a Child Theme Option: Enable users to create custom child themes for case studies, allowing for greater design flexibility and alignment with the overall website. (e.g. customize sections, fonts, and add new modules) Support for Multilingual Variations: Implement a similar system to the blog feature, allowing users to create different language versions of their case studies. (e.g. create a Italian version of a case study targeting the Italian market) Enhance Header and Footer Customization: Provide more flexibility in customizing the header and footer, including the ability to use custom CSS. (e.g. have more styling options for the menu items) I believe that by addressing these limitations, HubSpot can create a truly powerful and customizable case study tool.    What are your thoughts on these suggestions? Are there any other features you'd like to see added to the Case Study Beta?   ...その他を表示