Great minds think alike

Hello! I'm a Data Engineer, responsible for integrating HubSpot with our company's data warehouse. I'm currently working on transitioning our integration from APIv1 to APIv3 and have encountered a significant issue. At present, it's not possible to retrieve associated IDs for records obtained via the SearchAPI.   For instance, to fetch recently modified deals, I call the Deal SearchAPI with appropriate filters. However, I do not receive data about associated contact IDs for the located deals. In theory, one could construct a flow involving additional API calls to the AssociationAPI, but this approach is quota-consuming and not the optimal solution.   It would be beneficial to introduce a feature similar to the one available in the '/crm/v3/objects/deals endpoint'. With this endpoint, we can specify a parameter with comma-separated list of object types to retrieve associated IDs for.   Regards, Kuba ...read more

It would be great to be able to use GraphQL to load dynamic content in email templates.  For example, I have an Email that has be triggered by a deal in a workflow. In that deal is a custom object, lets say an Event. I would like the details of said event to appear on the email loaded via the triggering deal, and the Event ID in the deal and not by association.   {% set event = data_query.data.CRM.Event($id= personalization_token('deal.event_id', '0') ) %} or,   In an e-commerce email triggered by a deal,  a list of related products based on filters created by line items in the deal. AKA "You may also like" or "Other customers also bought".   {% set relatedProducts = data_query.data.CRM.ProductListFilter( filter: {product_category__in: ["pet food","flea treatment"]) %}   Regards, Jonathan ...read more

Hi, With the recent addition of Conditional Options (https://knowledge.hubspot.com/properties/set-up-conditional-options-for-properties), we are now able to set up conditional options through the HubSpot interface. However, at the moment, there's no easy way to set up conditional options through the API. And the process can be tedious for uses cases such as the Country <> State relationship, where a given country may have dozens of states to set up manually.   Therefore, could you please look into adding a new endpoint to the API? ...read more

GraphQL is a powerful tool that can be used (and currently is being used) in ways outside the CMS's scope. It's become a popular way to run advanced searches that the normal search endpoints can't handle. So why is it still paywalled in the pro and enterprise CMS plan? Every portal should have the ability to use GraphQL, just like every portal can use the search endpoint. There are a lot of things that people can't build currently because of their lack of access to GraphQL. Would love to see that changed. ...read more

It would be great if HubSpot, as some other CRM providers, could give us an api which would allow retrieving Contact photos. This would allow for applications to have same photos for Contacts as HubSpot web pages, which would improve user experience. ...read more

A contact can't resubscribe himself to a subscription type when he submits a form. As a test, I unsubscribed from a subscription type "ebooks" via the subscription preferences page, configured in my settings and displayed in my email at the bottom. I was still subscribed to other subscription types.   After that, I created a form where I put a checkbox to subscribe to "ebooks". To my surprise, people who submit the form, aren't resubscribed to the subscription type again, even if they select the checkbox which states that they want to be (re)subscribed. What's the difference between the subscription preferences page, and submitting a form with checkboxes where they can opt-in (again) to the subscription types selected? For us, this is a real show-stopper. We want to use the GDPR functionality, but it still needs to have some tweaking. We want to exclude the path where people unsubscribe via the subscription preferences page, request an ebook, and don't receive the email because they cannot resubscribe via a form submit, which includes the confirmation/checkbox of that subscription type. ...read more

I think that the ability to send programmatic in-app notifications using a Notifications API would be a great addition to HubSpot.   Use-Cases: 1. I have a swag system that sends swag packages to contact its connected to HubSpot using custom objects and it would be really nice if I could send a notification to the owner when a package is delivered. 2. When a HubSpot user hits the quota for contact prospecting, send a notification. 3. So many more use-cases    ~Carter McKay ...read more

I raised this issue with HubSpot support - and unfortunately recieved a less than helpful "this isn't a bug" response. But I am documenting it here for other people who will inevitably have the same or similar issue.   The problem: HubSpot's embedded forms have 2 callbacks that are very similar yet act very differently:   onFormSubmit onFormSubmitted   The main difference being the order in which they are executed, (onFormSubmit before onFormSubmitted). However, the main issue is how HubSpot executes these callbacks in the context of form field validation.   All hubspot form fields are validated prior to the onFormSubmit callback being run. EXCEPT the phone number field. The phone number field validation is performed AFTER the onFormSubmit callback executes. Which doesn't seem like a problem, until you realize that:   The documentation explicitly says: "Callback that executes after form is validated" The onFormSubmit callback is passed a $form argument that allows you to access the form field values (useful for any advanced redirect logic or tracking necessary post-submission). The onFormSubmitted callback is not passed this same argument - therefore the callback is practically useless if you need to access the form field data at the point of the submission lifecycle. So, if you utilize an onFormSubmit callback on a form that has a phone number field, and the form is submitted with an invalid phone number, the onFormSubmit callback will execute (even though it shouldn't as stated in the documentation).   This IS a bug, all other form fields are validated prior to the onFormSubmit callback being executed, but for whatever reason, phone number fields don't operate in this fashion.    PLEASE I beg you HubSpot - fix this. All fields should be valid before triggering either of those callbacks, and the current way it is built requires some extra hacky global variables to pass the $form object to the onFormSubmitted callback.   Also of note - the global callbacks suffer the same issues - the only difference being that the onFormSubmitted callback isn't passed a data property containing the form field values (similar to what is mentioned above).    My support ticket for reference is #8566325 ...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