Grandes mentes pensam igual

Hello guys,   How about the feature in marketplace to upload you own image preview for the email template. In my case I have a dynamic email template that does not have the option to add default content so the preview of the email template is not that nice. Let me know what you think. Cheers, Catalin ... Exibir mais

Pourrie-vous développer la fonctionnalité de bloquer les droits de suppression de tâches à certains utilisateurs.  ... Exibir mais

When uninstalling previously downloaded/installed themes, the theme still shows up in the downloads list. It's possible to end up with an overwhelming list of uninstalled themes - especially when clients download items indiscriminately to preview them!    We need a way to permanatly delete items from this list so items that were accidentally installed or that are very old can be cleaned up and no loger appear in the downloads area. ... Exibir mais

This is so desperately needed. No other company 3rd party connector has this feature and we have work with multiple.  We need to be able to fully customize the mappings between Shopify and HubSpot. When we make new Metafields in Shopify they need to be viewable during the mappings in HubSpot so we have total control of where we want data to flow in HubSpot and have the ability to select any property. Full customization would solve all our issues. The value this will bring is huge. Shopify is one of the biggest platforms with millions of users. This solution is not prevalent in the marketplace so by creating this you will be the only integration that has this solution. ... Exibir mais

For the love of something, I have no idea why this isn't a thing already. If someone downloads my app and then uninstalls, I need an event to be sent to my server to delete/pause their account and stop their subscription, if they have one. I need the option of doing some level of processing when my app is uninstalled. Please provide this option, it is mad necessary for app developers. ... Exibir mais

Hello! I have an idea for an expansion to the marketplace with customer contributed tools.   Workflow, Sequence, and Playbook open Community Marketplace.   It would be amazing if there was a Workflow, Sequence, and Playbook  Marketplace, where customers can post and share with the community. This would be extremely useful for those just getting started with Hubspot and for those seeking inspiration to solve a operational or sales problem.  ... Exibir mais

Wish we can attach a Jira ticket to Deal directly instead of creating a ticket and associate a Jira Ticket to the Hubspot Ticket.    Making a Ticket to associate the Jira issue is just waste of time and energy in our case.  ... Exibir mais

Who: theme providers in the asset marketplace, agencies/repeat customers, and new/promo customers What: purchase a theme at a reduced price using a promo code at time of purchase Value: save time for both the customer and the theme provider. Examples: just about every online purchase system offers a promo code option   Currently, theme providers have to process a partial refund to offer incentives to their customers, usually repeat customers like agencies through a multi-purchase discount or referral program. Ideally, the theme provider can setup and manage codes quickly and easily in the listing platform and easily monitor their use (or mis-use).   Really cool would be if a promo code could be assigned to a contact in the CRM, and auto-applied at time of purchase based on their email - a girl can dream, right? ... Exibir mais

We kindly request the review or removal of the undocumented HubSpot Asset Marketplace Theme requirement that prohibits custom modules from having the same label as default modules.   1. As theme creators, we strive to have greater control over our custom theme modules, and we believe that the labeling of these modules should not be restricted. The idea of using "Some prefix Button" or "Theme name Button" instead of simply "Button" module label appears illogical and unfriendly to end users, undermining the cohesiveness of the theme. Unfortunately, we find ourselves facing limited options: Prefixing all our custom modules with "Theme name...module" would result in peculiar and illogical module names. Since editors are already aware they are using our theme, there is no need to constantly remind them of it through module labels. Naming only the default-like modules with the prefix "Theme name..." would create an awkward disparity in module naming. For instance: Theme name Link Card Theme name Button Hero Image Finding an alternative naming approach could either compromise semantic accuracy or introduce redundancy: Using "Links" instead of "Link" or "Buttons" instead of "Button" raises semantic concerns. Employing names like "Link-bla" or "Button-bla" would appear redundant. Considering these limitations, we kindly urge you to reconsider this aspect and provide us with more flexibility in labeling our custom modules.   2. Since theme modules and default modules are already segregated into distinct tabs, namely "Theme modules" and "Common modules", it seems reasonable to conclude that having identically labeled modules in different tabs should pose no issue.   3. As an alternative solution, maybe this rule can be skipped when we hide official modules in our theme. So end user will not see two modules with the same label while using our Theme. our theme.json:     ... "hidden_modules": [ "@hubspot/rich_text", "@hubspot/button", "@hubspot/form", "@hubspot/linked_image", "@hubspot/icon", "@hubspot/divider", "@hubspot/horizontal_spacer", "@hubspot/text", "@hubspot/page_footer", "@hubspot/section_header", "@hubspot/header" ], ...       ***   We kindly request a thorough review of this specific rule. Thanks ... Exibir mais