Great minds think alike

Hello, Whenever Hubspot releases a new feature, I notice that you use a tool to guide the user on how to use the new feature on HubSpot. For example, clicking here triggers a note explaining what will happen. I'm aware that this is a solution developed and used internally. I can see other software providers offer this tool (Not that cheap) and it would be great if you could develop your internal tool in a way that can be used by your clients. ...read more

At the moment, when syncing a custom object FROM Salesforce to HubSpot, you are asked to create an association for contacts in HubSpot. Salesforce has both leads & contacts, and so when you are creating this association you are forced to chose which one you want to sync over.   This means that I am losing a chunk of data - for example, all the records that are leads in Salesforce are now not associated to my new custom object records in HubSpot.   I'd love there to be an option to be able to sync both to contacts in HubSpot - this is possible in the current SFDC <> HS integration; it just seems to be an issue with the custom object sync which is fairly new. ...read more

It would be great to have this integration support custom objects. ...read more

Hello,   It would be useful if HubSpot could be able to analyze the source of a property value.   For instance we would like for HubSpot to recognize when a lifecycle stage of a contact was set by source X (such as integration or CRM), have the property value Y.   This would allow us to say: "If the contact has a lifecycle stage set to Lead by the integration, then change the lifecycle to xxxx".   I guess this could be useful in many other ways to define workflows.   Have a good day,   Pierre ...read more

While working on an integration between HubSpot and a third party I'm facing a serious limitation of the private app's webhook event subscription tool.   Issues No filter Can't be controlled which objects are watched the changes for. Example: I want only the Country = Germany contacts to be watched for changes.   No optional properties Can't be added optional properties of the object to the change event data. Example: I want to receive the Country property of the Contact object in the event data, to be able to filter the incoming data on the integration side.   Proposed solution No filter Extend the webhook subscription tool with a filter as we have it in the workflows or lists.   No optional properties Extend the webhook subscription tool to let the user select some properties of the object, that will be included within every change event. The data could look like this:   { eventId: 12345, subscriptionId: 376543, portalId: 3247823, appId: 8907485, occurredAt: 1612817930264, subscriptionType: 'contact.propertyChange', attemptNumber: 0, objectId: 67235764, propertyName: 'email', propertyValue: 'test@gmail.com', changeSource: 'CRM_UI', sourceId: 'userId:3546436', objectProperties: { country: 'Germany', some_custom_property: 2356747 } }     Disclaimer: - it is not a viable option to get the data using the API, because we should be able to handle millions of data changes daily. - using workflows to filter the objects and trigger a webhook containing just the right data is not an option either, because without an API call can't be verified what property/properties were changed. ...read more

Surface App Information in Integration Settings from APIs     ...read more

I'd like to propose some enhancements to the Slack notifications feature within HubSpot workflows to make them more versatile and user-friendly.   Currently, when setting up Slack notifications in workflows, there are a few limitations that I believe could be improved upon:   Inability to Reorder Properties: It would be beneficial to have the ability to reorder the properties that should be attached to Slack notifications. Currently I have to delete all properties when I would like to add one on the first position, and re-add the other properties afterwards, which is quite time consuming and laborious, especially if you have a lot of properties to include in the Slack notification.  Lack of Text Styling Options: Currently, the Slack notifications sent from HubSpot workflows do not support text styling options such as bold, colors, font sizes, and other visual adjustments. Adding these styling options would enable users to highlight important information and improve the overall readability and aesthetics of the notifications.   By addressing these limitations, users would have greater flexibility and control over the Slack notifications generated by HubSpot workflows, ultimately enhancing their effectiveness in communicating important updates and actions to team members.   I believe implementing these enhancements would significantly improve the user experience and make the Slack notifications feature in HubSpot workflows even more valuable for teams. Thank you for considering this suggestion. ...read more

I would like to propose an improvement regarding the error messages displayed in the Workflow History section of HubSpot, particularly in relation to the WhatsApp integration.   Currently, when attempting to subscribe contacts to a WhatsApp subscription workflow based on their WhatsApp phone number alone, an error message is generated stating something like: "Neither an email address nor a phone number is present for the contact" (or in German: "Für den Kontakt ist weder eine E-Mail-Adresse noch eine Telefonnummer vorhanden"). Since a known WhatsApp phone numer is the trigger in this case, this message is misleading and does not facilitate troubleshooting efforts effectively.   Only upon closer examination of the enrollment history and contact details, we discovered a server response error code: "MISSING_SUBSCRIBER_ID" which helped us to realize that we cannot subscribe contacts to the WhatsApp service without prior opt-in messages from them:   Misleading Error Message in HubSpot Workflow History   Consequently, despite having diligently collected consent for WhatsApp conversations via a form, the workflow remains ineffective (the whole problem is stated in this community post, by the way).    To improve user understanding and streamline troubleshooting processes, I suggest revising the error message to provide clear insight into the underlying issue and potential solutions. ...read more

Hello!   Reclenty, i was talking with Hubspot support channel and I got a problem that has no solution at now.   In Brazil, we have an issue with the DDD (area code) of some regions. In these regions, cell phones start with a extra 9 at the beginning. +55 XX 9.XXXX-XXXX So, when using WhatsApp message sending automation, the issue appears. It is possible to send the message normally through automation, however, when the lead responds the problem begins.   To deal with this problem, WhatsApp simply suppresses the extra 9, treating the contact as if this additional number did not exist. However, when the lead responds, WhatsApp forwards the message to Hubspot without the extra 9.   The problem: When the message is sent, the recipient has 9 numbers, when it is received on Hubspot, it only has 8.   1) The contact is not automatically associated, because the numbers (sender and receiver) are differente 2) Automatic message tracking is lost, sellers have to guess which automatic message was sent previously 3) Now salespeople have 2 manual and repetitive activities to perform (associate the contact and guess which message was sent), taking up their time to sell - creating friction in the sales process.   I believe that Hubspot has several Brazilian clients who also go through this, which is why I bring the discussion here. ...read more