> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/pre-requisites-for-integrations/hubspot/hubspot-configuration.md).

# Hubspot Configuration

<figure><img src="/files/zljGMeZpR3NMI30T1WNL" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/hpW2iut539brSFnPKtqt" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="169">Field</th><th width="146.66668701171875">Description</th><th width="309.666748046875">Why It Is Required for HubSpot Integration</th><th>Example Value</th></tr></thead><tbody><tr><td><strong>Web Service URL</strong></td><td>The base URL of the HubSpot REST API endpoint that the connector will communicate with.</td><td>The integration requires the HubSpot API endpoint to send and retrieve data such as Contacts, Companies, Deals, Products, and Tickets. Without the API URL, the connector will not know where to make requests.</td><td><code>https://api.hubapi.com</code></td></tr><tr><td><strong>API Key</strong> <em>(Preferably Access Token in HubSpot)</em></td><td>Authentication credential used to authorize requests to HubSpot APIs.</td><td>HubSpot no longer supports API Keys for most integrations and recommends using a <strong>Private App Access Token</strong>. This token validates the identity of the connector and grants access to HubSpot objects based on assigned scopes.</td><td><code>pat-na1-xxxxxxxxxxxxxxxxxxxx</code></td></tr><tr><td><strong>Object</strong></td><td>The HubSpot CRM object that will participate in the synchronization process.</td><td>The integration needs to know which object to create, update, or fetch from HubSpot. Different APIs are invoked depending on the selected object.</td><td><code>contacts</code>, <code>companies</code>, <code>deals</code>, <code>products</code>, <code>tickets</code></td></tr></tbody></table>