![]() The propertyValue in the webhooks payload will always be FALSE.Webhooks are a very popular and simple integration mecanism that allow services to notify each others about different types of events. isArchived: the conversation thread has been restored.In the webhooks payload, the propertyValue will either be OPEN or CLOSED. status: the status of the conversation thread has changed.If the thread was reassigned, the propertyValue will be an actor ID in the webhooks payload if unassigned, it will be empty. assignedTo: the conversation thread has been reassigned or unassigned.If you are using the conversations messages and inbox API, which is currently in beta, the following properties are available: If a customer's account doesn't have the property you specify in a subscription, you will not get any webhooks from that customer for that property.Ĭertain properties are not available for CRM property change subscriptions. You can specify multiple property change subscriptions. If you set this limit too high, you may saturate the resources available to your endpoint which could result in slow responses, notification delays, or your endpoint becoming unresponsive.įor property change subscriptions, you will need to specify which property you want to be notified of.If you set this limit too low, notifications might time out if there are too many notifications sent to your API and the limit is saturated for more than a few seconds. ![]() Setting this limit helps HubSpot send you notifications as fast as possible without putting too much load on your API. For example, if you have a limit of 1 request per 10 seconds, if 1 request is sent, HubSpot will wait for a response or for 10 seconds to pass before sending another request, which ever comes first. This throttle limit is a concurrency limit, so as soon as there is a response to a request, the total active requests will be reduced by one and another request can be sent. You can also adjust the event throttling limit, which is the number of concurrent requests your endpoint can handle. You can subscribe to CRM object events, which includes contacts, companies, deals, tickets, products and line items, as well as conversations events.īefore setting up your webhook subscriptions, you need to specify a URL to send those notifications to. Any account that install your app by going through the OAuth flow will be subscribed to its webhook subscriptions. ![]() Webhooks are set up for a HubSpot app, not individual accounts. That you deploy a publicly available and secure (HTTPS) endpoint for that URL that can handle the webhook payloads specified in this documentation.See the prerequisites documentation for more details about creating an app. That you set up a HubSpot app to use webhooks by subscribing to the events you want to be notified about, and by specifying a URL to send those notifications.Using the Webhooks API requires the following: Webhooks can be more scalable than regularly polling for changes, especially for apps with a large install base. You can configure subscribed events in your app’s settings or using the endpoints detailed below. ![]() Rather than making an API call when an event happens in a connected account, HubSpot can send an HTTP request to an endpoint you configure. The Webhooks API allows you to subscribe to events happening in a HubSpot account with your integration installed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |