> 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/guides/enrich-and-writeback.md).

# Fill missing data and write it back to the CRM

Use Records actions to enrich a known selection and update only the CRM fields your team chose.

## Prepare

Connect the CRM and a Records-supported enrichment provider. Review your [Field catalog](/data-and-integrations/field-catalog.md) and choose the destination fields.

## Run the actions

1. Find the People or Companies in Records and select the intended rows.
2. Run **Fill gaps** to add missing values. Choose **Enrich** only when replacing values is intended.
3. Inspect **Recent runs** and individual outcomes.
4. Run **Link to CRM** for the selection and check the matched destination IDs.
5. Run **Push to CRM** with explicit source-to-destination field mappings.
6. Inspect the destination record and values.

Push to CRM updates linked records; it does not create unmatched records. It skips blank source values rather than clearing destination fields.

## Keep failures visible

A batch can contain mixed results. Inspect skipped, unmatched and failed rows instead of treating the overall batch as evidence that every person was updated.

Provider lookup and CRM writeback are separately billable/operational events in your connected accounts. Test a small, known selection before a larger run.

Do not reuse a workflow-only provider chain without checking [Provider support](/data-and-integrations/provider-support.md).

See [Fill gaps](/records/fill-gaps.md), [Link to CRM](/records/link-to-crm.md) and [Push to CRM](/records/push-to-crm.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/guides/enrich-and-writeback.md?ask=<question>&goal=<user_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.