Great minds think alike

Conditional stage properties are currently not exposed and visible when you connect to a HubSpot account via API. So one can't see these rules on deal pipelines when managing data via API.  ...read more

I am finding that lately, as I have been working in this portal for some time now, I have developed a substantial code-base that is relatively re-useable, at least for myself and other devs. Instead of dual-tabbing and copying and pasting my code and settings etc, it would be nice to see the ability to save custom coded actions, not so disimilar to how I can save custom coded modules in the CMS.  This would save me time sigificantly as, let's say that I want to clone an action:  I need to either check my existing repositories OR remember which workflow used a similar action. I then need to copy and past out the values, add in any inputs etc all manually, and save it out.  Conversely, if I were able to select something like "Saved Custom coded actions > Get Associated [3rd Party Name] Data" Anytime I need to access a custom bit a code I already wrote, I can just add it in, and update the 'template' as needed. Double points if we could lock these down to only Super Admins or some other permission set, so I can avoid user confusion.  ...read more

I've had several meetings in Google Calendar, that I tried to move from one Sales person to another. When updating the Sales person, the meeting did successfully move from one calendar to the other within Google, but got deleted in HubSpot. Therefore there was no meeting visible and some workflows that are based on it, broke.   Therefore I'd suggest to find a solution to not delete the meeting, but just update the user. ...read more

We have been playing around with the new direct HubSpot to WhatsApp integration. But we have run into a limitation around business-initiated messaging and managing the required Opt-In according to the Meta/WhatsApp guidelines for Opt-In.    Today HubSpot only supports setting the opt-in communications subscription preference either through: Customers explicitly opting in through the use of a keywoard like START or SUBSCRIBE in a customer-initiated WhatsApp conversation, or Manually setting the preference through the HubSpot App UX; and only one contact at a time, no bulk updates Meta/WhatsApp allows for explicit consumer opt-in to be gathered through multiple channels: SMS Website In a WhatsApp thread By phone (using an interactive voice response (IVR) flow) In person or on paper (customers can sign a physical document to opt in) However the HubSpot approach today only covers one of these channels: "in a WhatsApp thread."   In our use case we get explicit opt-in through a web form. So it would be ideal if we could push this opt-in through the Subscription Preferences API, just like we can for email opt-in/opt-out. ...read more

Hi all,   I've contacted Hubspot Support regarding Server Side support and they told me there is no official support (there are some workarounds from 3rd party members). I said thank and if they could relay it to their engineers that Server Side tracking is essential for many companies as cookies are very blocked and many people use ad block. They told me to post my idea on this forum.   Any chance Hubspot is working on supporting Server Side tracking or would be willing to take it up on the roadmap?   Best, Kai ...read more

This idea is based on the following comment. Please upvote it.   To be able to export the manually inputted forecast data via an API or any ETL tool, as to have this data in our warehouse.   The data is needed by RevOps to report numbers, run analysis and understand the sales people performance over time and our active markets.   We want to use the forecasted data report up to management, run forecasts analysis and understand sales performance accuracy. Since this data is a manual input, it adds values to our knowledge pipeline for the sales representative and market.   For example, Karim, a representative working in France, will add week by week a forecast of their sales quota. Right now, we need to manually extract this data to run in RevOps our market forecasts. By having this data in the warehouse, we will increase the speed of delivery for forecast and reduce friction in passing this data to other parts of the organization.   ...read more

We have to define the objectTypes that a custom workflow action supports explicitly (or leave it blank for "any object"). Because custom objects have per-portal objectType ids -- we cannot have a workflow action that just targets custom objects.   Instead we have to open it to "any object", which leads to people accidentally trying to use the workflow on objects like a Contact.   We also don't get the objectType on which the workflow is running, which causes us to have to prompt users to manually select one so we know what objectType to make API calls against when the custom workflow action runs. ...read more

Support user provisioning for Azure AD.   For example provide similiar resource or API documentation like this: https://knowledge.hubspot.com/account/provision-hubspot-users-with-scim-through-okta   *** Posting on behalf of a customer ...read more

One of the strategies to sync Hubspot and any database is using the property 'hs_lastmodifieddate'.   The idea is to use the search endpoint and return just the objects that has 'hs_lastmodifieddate' after then last sync. So the sync is fast and cheap.   The problem is that when user associates/dissociates any object, the property 'hs_lastmodifieddate' doesn't update, excecpt in cases where the property "number of associated X" exists. For instance, when a contact and deal are associated, the property "number of associated contacts" on deal is updated and, then, the 'hs_lastmodifieddate' updates (due to property change, not association).   The other solution to that is always read all records for syncing, to ensure all associations are updated, the problem with that endpoint is that when the number of properties is too long it raises 414 error (the search api does not requires properties as params in URI). ...read more