Great minds think alike

HubSpot has many APIs which require a "PUT" request type. However, "Send a webhook" Data Ops action in Workflows only allow "POST" or "GET".   "Send a webhook" should allow "PUT" as a request type so we can trigger workflows to HubSpot's API endpoints that require "PUT", e.g. https://developers.hubspot.com/beta-docs/reference/api/marketing/subscriptions-preferences/v1?uuid=4a3d8780-4798-4c40-89dd-3d4e1d7ee3c9#update-email-subscription-status-for-an-email-address   (You might ask why we have to use HubSpot's API in the workflow, and that is because for reasons that are unclear HubSpot does not allow unsubscribing someone from all email via a workflow). ...read more

Dear Hubspot community and Hubspot product teams,   Context: We are implementing a more complex data model across standard objects and custom objects and have ran into the limitations of standard out of the box connector for Salesforce. This resorts us to create custom integrations.   Problem statement: in order to have more real time integrations, we want to have an event based integration instead of a polling based. When a record is created for a custom object in Hubspot, we would like to trigger the integration, currently the Webhook API in hubspot only supports standard objects.    Workaround: as a workaround, we are required to use the OperationsHub license and introduce a Workflow with Webhook step to trigger our middleware after a custom object record has been created.   Idea: can you introduce the usage of custom objects to your Webhook API allowing us to avoid the license of OperationsHub and avoiding the need to build Workflows with Webhook steps.  This will also be more aligned with the other API's that already support Custom Objects e.g. Create Read Update Delete.    Thanks, Wouter ...read more

We use a large number of custom objects, and it's getting to the point where seeing the 'custom object' icon is getting a bit ugly for me. I would like the ability to provide a custom icon for these objects.  I would be ok with being able to just select from a template/color selector, if that would be easier for HubSpot to implement.  However, I think it would be much cooler to allow us to upload PNG/SVGs to our file manager and reference those in our Custom Object schema.    ...read more

We would greatly appreciate the ability to set the display order of custom event custom properties.    When creating a custom event (via API or otherwise), you create a a set of custom properties relevant to that event, in addition to the default properties like "occurred at," "device," etc. Depending on how your custom events are triggered, these custom properties will display on the relevant object's timeline when a custom event completion is posted.   Current state: the custom properties for that custom event will display in a seemingly random order (HubSpot support has told me it sorts alphabetically based on the display label, but this is not what we are observing). This means that properties that provide context to other properties (e.g. one for date, one for time) will display out of order and cannot be organized neatly for the end user reviewing them on the timeline.   Desired state: allow the admin to set the display order of custom event properties so they display in a set hierarchy when event completions are posted. The API call will *accept* the display order being included, but it will ignore it.   Also, please add an idea category for custom events! ...read more

I want to create a Lead with only a Company as the primary association. When looking at the association IDs page it seems this associationId has not been created. It is not possible to create the Lead on its own and then associate the Company as I get this response { "status": "error", "message": "A LEAD_TO_PRIMARY_CONTACT or LEAD_TO_PRIMARY_COMPANY association is required to create a LEAD object.", "correlationId": "e0d9667e-ee86-43e6-9472-caf0bda1fa1b", "category": "VALIDATION_ERROR" }   Can we please get an associationID for LEAD_TO_PRIMARY_COMPANY  ...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

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

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

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