Great minds think alike

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

I'm trying to use HubSpot batch API and have the next problem: when I send 3 contacts to https://api.hubapi.com/crm/v3/objects/contact/batch/create and if one of these contacts has a problem - HubSpot response format is like this: { "status": "error", "message": "Property values were not valid: ......." "correlationId": "2c2b03e3-5692-4261-b462-0bea1952e562", "category": "VALIDATION_ERROR" } Why the response format is not like this: [ { "status": "error", .... }, { "id": "4136413868", .... }, { "id": "4136413870", .... } ] ...read more

Summary: Ticket created via API should work with the same Help Desk features as tickets that are created via email, so that all tickets can be handled equally. Currently, API-created tickets are lacking core functionality, such as Agent Presence indicators and some ticket routing/auto-assignment features. More details: Agent Presence (indicating when another agent is currently actively looking at a ticket, so that other agents don't try to work on the same ticket at the same time, preventing accidental agent collisions) is something we'd been promised in the regular Tickets interface for years and years, but later we were told we'd have to migrate to HelpDesk to get it... But it turns out that Tickets created via API (which is our primary method for ticket-creation) don't qualify for Agent Presence of various other HelpDesk features (including some ticket routing/assignment automations, etc.). Some tools, including Agent Presence indicators, only work when a ticket is either created via email, or after an email exchance is created from within the ticket. Apparently this is due to these features being tied exclusively to "Conversations," but an API ticket is not a Conversation until an email message is involved.... I get that a Conversation = an email message... But I don't understand the logic that a Ticket doesn't deserve Agent Presence or auto-assignments until after a manual Conversation has started -- at that point, for API-generated tickets, Presence and assignments are not very useful anymore, because by the time a Conversation has started an agent has already engaged with the ticket. The agents need to be able to see that someone is already looking at a ticket (and/or the ticket needs to be correctly routed and assigned) right at the start, where most agent collisions occur in the first place. If anything, API-generated tickets should allow for even more advanced functionality, as determined by the API settings, rather than being treated as 2nd-class tickets with more limited abilities. ...read more

It would greatly improve our WhatsApp integration if HubSpot could automatically capture any user-initiated WhatsApp message—whether from the embedded chat widget or direct WhatsApp app—and: Auto-upsert contacts by phone number when a new user messages for the first time. Log inbound messages on the contact’s timeline and surface them in the Conversations inbox without manual copy-paste. Trigger workflows (opt-in, welcome series, unsubscribe handling, qualification flows, etc.) based on the inbound message or detected keywords. Allow chatflows to ask for custom fields (name, email, phone) directly in-chat, mapping replies back to HubSpot contact properties as part of the chatflow builder (no external middleware required). Use Case: We’ve connected our WhatsApp Business number and can send approved HSM templates outbound via workflows, but we cannot yet: Automatically create a new contact when an unrecognized number messages us. Sync their replies into HubSpot without manual record edits. Drive post-reply logic in chatflows based on those messages or property updates. Adding first-class support for inbound message capture, contact upsert, and chatflow-driven data collection would close the loop on the entire WhatsApp customer journey, reduce manual work, and let us build fully conversational lead-capture forms inside WhatsApp. Benefit to HubSpot Community: Many customers use WhatsApp as a primary support and sales channel. Native inbound sync and chatflow data collection would: Eliminate middleware complexity. Surface customer conversations in HubSpot automatically. Unlock powerful workflow triggers on live inbound messages. Reduce friction when building multi-step conversational forms. Please let me know if there’s any additional context I can share—and thanks for considering this enhancement! ...read more

We could use a more condensed Table component. The existing Table component has way to much top and bottom padding. We want to be able to create a table with normal padding, as seen on the CrmAssociationTable component.   The current Table component is visually distracting for users. We just need to show them some record based data in a format they're used to seeing in HubSpot. I hope this is somewhat of an easy add since the more condense table styling used in CrmAssociationsTable is used throughout the CRM and in UI extensions already. ...read more

I propose adding the ability to include alternative products and optional products in HubSpot quotes.   Example for Alternative Products: A customer receives a quote for the “Premium” product and can choose “Basic” as an alternative. This allows the customer to select between two options directly within the quote, making it more transparent and flexible.   Optional Products: Additionally, there should be an option to include products or services offered on an optional basis (e.g., add-ons) without affecting the total price. Customers can choose to add these optional products if they’re interested, enabling a more tailored quote experience.   If implemented, it’s essential to ensure that the API also supports this feature, allowing line items to be linked with the quote and designated as either optional or alternative.   Many other platforms already offer this functionality, and it would empower HubSpot users to better adapt quotes to customer needs, increasing both flexibility and customization. ...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

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 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