> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/hubspot.md). # HubSpot Connect HubSpot to match existing customers, route by owner and write back the outcome of a lead journey. ## Connect the workspace An admin opens **Settings → Integrations → HubSpot** and completes authorization for the intended HubSpot account. The standard connection screen requires you to disconnect Salesforce before connecting HubSpot. Open CRM settings after authorization. Choose the routing and booking behavior you want, then map your members to their HubSpot owner identities in [Connected identities](/settings/identities.md). ## Build a workflow Use **HubSpot Match** to find a record before deciding whether to create one. Branch on Matched and No match. Read the matched owner, then apply your [Ownership and fallback](/routing/ownership-and-fallback.md) rules. Create and Update steps write the fields you map. Association steps connect supported records; engagement steps work with supported activities. A company match alone does not associate a contact automatically. [CRM mirror](/integrations/crm-mirror.md) supplies stored fields for Records and lead context. Match steps are the better choice when the decision needs a current provider lookup. ## Check the result Inspect the actual HubSpot record ID, object and owner in the workflow output. A simulated match is sample data. Run a controlled live test before relying on owner mapping or custom property writes. For follow-up, see [HubSpot sequences](/integrations/hubspot-sequences.md). For website capture, see [HubSpot forms](/forms/hubspot.md). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/integrations/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 `build a script that syncs our docs to a CMS` 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.