Great minds think alike

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

We are currently recording our sales meetings within Google Meet and once that meeting is done, the recording gets saved back onto Google Calendar as an attachment after the meeting.   It would be very convenient if then that attachment (which is the meeting video) link of the recording of the video (that gets saved back to the calender and in Gdrive anyways) would also be automatically saved to the appropriate contact via syncing the attachments from Gcalendar.   Right now it is a manual process and when you are back to back with meetings this creates an extra task of having to go back and save them to the CRM. This will help tremendously with efficiency and referring back to the meeting video for details when trying to close a sale.    ...read more

There is no API access to property restrictions rules like "Date not in the past" or "Number must be positive". Portal admins can create these restrictions and our API calls will fail if we try to send invalid data.   We have to work around this because if we send invalid data as part of a bulk update, the whole update fails -- so we have to pull out the invalid data and retry.   Additionally we cannot do any kind of validations in our product on these properties when we are collecting the user-input. We've had customers use these restrictions and then failed to sync because of validation rules.   This is generally useful for HubSpot apps that write to user-defined properties. ...read more

Idea / Request / Recommendation: Hubspot should automatically apply existing "conversion source" logic to the Custom Events "touchpoint" property, when Custom Events are tracked via JS, API, or Visualizer.   The Hubspot Custom Events Tool [accessed by going to Reporting & Data > Custom Events, or via https://app.hubspot.com/events/123456789/manage {where your account ID replaces 123456789}] automatically creates a default event property called "touchpoint source", which has the internal name hs_touchpoint_source.    There are 4 ways of creating event data: Visualizer Spreadsheet import Javascript API For the latter 3 (Spreadsheet, Javascript + API), users are expected to define the touchpoint source from the list described at https://developers.hubspot.com/docs/api/analytics/events#interaction-sources. Yet in the latter two cases (Javascript + API), the code a user might need to write in order to get and populate the appropriate data is a replication of existing Hubspot code: Hubspot already knows the "latest converstion source" data for these user actions. It just needs to be applied to the Custom Event data.   Worse yet, for the first method (Custom Events tracked codelessly via the Events Visualizer) it's actually not possible to define the touchpoint source. So these events lack the critical source information that would make them useful marketing data.   Thus, my recommendation:   Hubspot should automatically apply "conversion source" logic to the Custom Events "touchpoint" property, when Custom Events are tracked via JS, API, or Visualizer.   ...read more

I need to get recently archived objects (e.g. contacts) for the last week. I am sending a request: GET https://api.hubapi.com/crm/v3/objects/contacts?limit=100&archived=true But the response isn't sorted by any of the fields. So, I need to get all archived contacts (10 pages). Please add a sort={field}&direction={ASC,DESC} (e.g. sort=archivedAt&direction=DESC in my case) parameters to GET /crm/v3/objects/{object}. ...read more

A batch endpoint for custom events would be great as we are going over the API threashold by sending single calls.  This is the single event end point link that we would like a batch version for; https://developers.hubspot.com/beta-docs/reference/api/analytics-and-events/custom-events/custom-event-completions#post-%2Fevents%2Fv3%2Fsend ...read more

Hi Community,  I'm reaching out to request assistance with retrieving data for a specific Call-to-Action (CTA) via HubSpot's API. I've reviewed the documentation, but I'm having trouble figuring out that there is no API available for this.   It would be great if HubSpot could provide this functionality.    Thanks! ...read more

Hi team, sharing this here as I recently worked with a customer with the following problem: Customer deleted a property and wanted to recreate it as a unique property but run into the following error: message: "The following property cannot be created with hasUniqueValue=true because a non-unique property with the same name previously existed in this portal The proposed workaround is for the customer to create a new property with a new name or create this property as a non-unique property. Ideally, it would be good if we could look into into the possibility of fully purging properties when deleted.  ...read more

The CMS search API currently only searches for content based on each individual keyword in the search input. So if I search for 'Affordable Care Act', then results that contain either 'Affordable', 'Care' or 'Act' are returned.    There is no way to limit search results to only include content that contains the full string of 'Affordable Care Act'. Google supports this search behavior by allowing users to encapsulate the search term in quotes such as "Affordable Care Act".    Without this feature, the Search API returns many results that are useless to the user if their search contains commonly used words, in this case, 'care', and it is harder to find content relevant to their interests.  ...read more