> 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/crm-mirror.md). # CRM mirror CRM mirror brings selected HubSpot or Salesforce fields into Distro's stored people and companies. Use it for reusable lead context and Records actions. ## Set it up 1. Connect the supported CRM and confirm the workspace. 2. Open the CRM mirror controls. 3. Choose the supported objects and fields to mirror. 4. Check field mappings in the [Field catalog](/data-and-integrations/field-catalog.md). 5. Inspect a known email or domain in [Records](/records/browse.md) after a sync. The regular mirror runs on an hourly schedule. A saved record is a snapshot; use a workflow Match step when you need a live CRM decision. ## Understand the direction Mirror supplies data to Distro. It is separate from [Push to CRM](/records/push-to-crm.md), which explicitly writes selected fields back to an already linked CRM record. A workflow CRM trigger also has its own conditions, cursor and execution. Do not assume an imported mirror record starts every workflow. ## Troubleshoot missing fields Check whether the object and field were selected, whether the connected user can read them, and whether a sync has run. Look at the expected person's email or company's domain rather than searching only a display name. Source-labelled CRM properties can coexist with form and enrichment fields. Review the picker and mapping before using a similarly named field in a routing condition. --- # 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/crm-mirror.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.