> 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/records/link-to-crm.md). # Link records to your CRM **Link to CRM** finds an existing CRM record and saves its identity on the Distro record. It does not create a CRM record or copy every CRM property into Distro. ## Link a selection 1. Connect your workspace's [CRM](/data-and-integrations/crm.md). 2. Open **Records** and select up to **250** records. 3. Choose **Run an action → Link to CRM**. 4. Select **Run** and review **Recent runs**. 5. Inspect a known person or company and confirm the linked CRM identity. People are looked up by email. Companies use domain-based lookup: HubSpot companies by domain, or a Salesforce Account website search. For teams connected to both CRMs, this action chooses HubSpot when it is connected, then Salesforce otherwise. It is not a simultaneous match against both systems. Use explicit provider-specific workflow steps when your journey must target a particular CRM. ## If there is no match Check the email/domain and confirm the record exists in the connected CRM account. A “no CRM match” result does not mean the person was deleted from Distro. Keep a separate path for leads that need a new CRM record. If duplicates could match, inspect them before writeback. This record action does not provide the configurable match priorities available in workflow CRM steps. ## Use the link Once linked, [Push to CRM](/records/push-to-crm.md) can write selected values to that record. Review the provider, object and record identity before running the write. --- # 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/records/link-to-crm.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.