> 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/fill-gaps.md).

# Fill missing record fields

Use **Fill gaps** when you want new data without replacing fields that already have values.

## Run Fill gaps

1. Open **Records** and select up to **100** people or companies.
2. Choose **Run an action → Fill gaps**.
3. Choose an **Enrichment chain** or a supported **Single provider**.
4. Select **Run**.
5. Review the processed and changed counts in **Recent runs**.

For example, use it to add missing job titles after importing a list. Existing non-blank values are retained when the new data is merged.

## Choose the provider carefully

Records enrichment tries supported connected providers in chain order and stops at the first provider that returns data. It does not merge all chain providers the way workflow Enrich Lead does.

The provider must work on the Records surface. Wiza, Harmonic and Amplemarket currently work through workflow enrichment rather than this action. See [Provider support by surface](/data-and-integrations/provider-support.md).

## After the run

A record can stay unchanged because nothing was missing, no data was found, or a provider was unavailable. A completed batch can contain individual failures; compare processed and changed counts rather than treating Done as “every record updated.”

Fill gaps updates Distro records. It does not automatically update your CRM. Review the values, then use [Push to CRM](/records/push-to-crm.md) if you want a deliberate writeback.


---

# 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/fill-gaps.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.