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

# Enrich selected records

Use **Enrich** to refresh selected Distro records with provider data. Unlike Fill gaps, enrichment can replace stored values when the provider returns a new value.

## Run enrichment

1. Open **Records → People** or **Companies**.
2. Select up to **100** records.
3. Choose **Run an action → Enrich**.
4. Choose a chain or a supported single provider.
5. Review the displayed provider-call estimate, then select **Run**.
6. Check **Recent runs** and inspect a few changed records.

The action tries chain providers one at a time. The first provider with data supplies the result. Providers without a Records adapter, disconnected providers and paused providers are skipped.

## Before using a chain

Check [Provider support](/data-and-integrations/provider-support.md). A provider appearing in the chain editor does not mean it can run on every surface. Records currently supports Apollo, Clearbit, People Data Labs, Crustdata, ZoomInfo and Ocean through its single-provider path; saved chain choices are narrower.

Provider calls use your own connected provider account. A successful no-match lookup can still count as usage under the provider's terms.

## Decide whether to write back

This action saves data in Distro. It does not create or update CRM records. Use [Link to CRM](/records/link-to-crm.md), review your field mapping, and run [Push to CRM](/records/push-to-crm.md) separately when the destination should change.


---

# 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/enrich.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.