クリエイティブな才能を開花させよう

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 ...その他を表示

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. ...その他を表示

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.   ...その他を表示

The current ConnectWise PSA HubSpot integration does a great job of syncing most properties between ConnectWise Companies, Contacts, and Opportunities (HubSpot Deals).    However, there is a major gap: The opportunity financial data does not sync. This means that when connecting to HubSpot to view all the ConnectWise opportunities, they all amount to $0. This ruins over 50% of HubSpot's dashboard features and doesn't allow sales teams to use HubSpot as intended.    I would like to request that ConnectWise Opportunity Forecast Data be synced (2-way) and allowed to be mapped to the Amount or Forecasted Amount fields in Hubspot.    Thanks for your time and attention, developer team! ...その他を表示

Hubspot currently "strongly recommends" that the access token for each private app be rotated once every 6 months.  However, this process requires a Hubspot administrator to manually log into the UI to generate a new token, provision that new token to the app, and following tests, to revoke the old token.  In general, this requires probably an hour's worth of time, when you factor in the need to redeploy and reverify the software using the private app, before deactivating the old token.  Given that we have 6 (and counting) private apps, for which we store/provision the tokens securely, this essentially requires an administrator to waste a full day every six months fulfilling a security requirement.   The primary risk factor that necessitates the need for regular rotation is the fact that Hubspot's API utilizes the access tokens as long-lived bearer tokens in and of themselves.  Therefore one way to eliminate the need for access token rotation would be to support an alternate method of authentication, either:   1. Support an OAuth 2 Client Credentials flow such that the client secret is transmitted solely in the request for an API access token with a limited lifetime, which is then used to make the actual API requests.  This change would reduce the transmission of client secrets over the network to a limited number of tightly-controlled API calls, thereby mitigating the likelihood of compromise such that rotation is unnecessary, or at least not as frequent.   2. Utilize a request signature (a la OAuth 1 or AWS) such that the client secret is never transmitted in any request, and therefore the risk of secret compromise lies entirely with the client, thereby delegating the need for rotation to the client themselves.   If neither of these options are going to be implemented, and therefore regular rotation of private app access tokens will continue to be a requirement, then Hubspot should provide APIs such that the rotation of access tokens themselves can be automated by a separate private app, such that an administrator's time need not be required to accomplish the rotation requirement. ...その他を表示

Wir erstellen Tickets im Helpdesk mit einer API und füllen die Ticket-Eigenschaften mit den Werten aus einem eigenen Formular. Problem: Alle Tickets kommen mit Kanal "unbekannt" rein.  Ich möchte via API einen individuellen Kanal X für die Eigenschaften "Account des Ursprungskanals" und/oder "Typ des Ursprungskanals" mitgeben.     ...その他を表示

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.    ...その他を表示

API endpoints for managing Deal Collaborators through the HubSpot REST API, allowing programmatic access to manage (add/remove) collaborators on deals. ...その他を表示

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.    ...その他を表示