> 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/push-to-crm.md). # Push record fields to your CRM **Push to CRM** writes chosen Distro fields to an existing linked CRM record. Use it after checking enrichment or imported data. ## Before you start Link the records with [Link to CRM](/records/link-to-crm.md). Check that the connection can edit the destination properties and that the linked record belongs to the intended CRM account. ## Choose the fields 1. Open **Records** and select up to **100** records. 2. Choose **Run an action → Push to CRM**. 3. Enter one field pair per line, with the Distro key on the left and the CRM API name on the right. 4. Add between **1 and 10** field pairs. 5. Review the selected records, then select **Run**. For a linked HubSpot contact, a mapping might be: ``` title=jobtitle phone=phone ``` Use real property API names, not their display labels. A Salesforce mapping might instead use `title=Title`. ## What happens The action updates the linked record; it does not create a missing record. Blank source values are omitted, so this action is not a way to clear a CRM field. Unlinked records are skipped rather than guessed. Check **Recent runs**, then inspect a controlled destination record in the CRM. A changed count tells you how many records were written, not how many fields were written everywhere. For conditional updates, record creation or explicit field clearing, use [CRM workflow steps](/workflows/crm-steps.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/records/push-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.