> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/primer-support-review/section-connections/integrations/connecting-a-crm/hubspot.md). # HubSpot Connect HubSpot read-only, with or without contacts, so Primer can build audiences from your CRM. Primer connects to HubSpot over OAuth to read your contacts, companies, deals and lists. The connection is **read-only** — Primer never writes back to HubSpot. ## What Primer reads When you authorize the connection, Primer requests read access to: * Contacts, companies and deals * Lists * Deal, custom-object and custom-property schemas * Forms Custom properties and custom objects are read through the schema and custom-object scopes, so audiences can filter on your custom HubSpot fields. ## Full vs. companies-only You choose how much Primer reads: * **Full** — includes contacts (people). Primer reads both companies and contacts, so you can build person-level audiences and exclusions from your CRM. * **Companies only** — Primer reads companies but **not** contacts. Use this if you don't want to share contact records. In this mode Primer can enrich and target at the **company** level (build company audiences, suppress existing-customer accounts), but it has no contact records to build person-level audiences from. Switch to **Full** later if you need people. ## Connecting Authorize Primer from the connections screen and approve the requested read scopes in HubSpot. To change between full and companies-only, reconnect and pick the other mode. To disconnect, revoke Primer's access from HubSpot or remove the connection in Primer. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.sayprimer.com/primer/primer-support-review/section-connections/integrations/connecting-a-crm/hubspot.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.