> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/integrations/enrichment.md).
# Enrichment
Use enrichment to add person and company information to Form Router submissions. Routing rules and CRM mappings can use the fields returned by your connected providers.
Workspace admins manage enrichment in **Settings → Integrations → Data enrichment**.
## Connect a provider
Choose **Connect** on Apollo, People Data Labs, Clearbit, Crustdata, ZoomInfo, or Ocean. Enter the requested credentials and choose **Enrichment coverage**:
* **People and companies** requests person and company information when the required identity is available.
* **Companies only** uses the submitted work-email domain for company information.
ZoomInfo requires a client ID and client secret. Clearbit uses an existing legacy secret key and asks for a **Test email**; saving can count that lookup against your plan. Crustdata needs a submitted LinkedIn profile for person enrichment.
Read the connection page’s verification notice before saving. A successful credential check does not guarantee that your provider account can return every field. Check permissions and credits if live requests show **Needs attention**.
Connecting a profile provider adds it to the default waterfall order. Actual enrichment runs when a Form Router’s rules or workspace CRM mappings require it.
## Choose the provider order
From **Data enrichment**, open **Configure waterfall**. In **Default provider order**, move providers using their drag handles or up and down controls. The order is saved when you move a provider.
Distro checks that order separately for each requested field and keeps the first non-empty answer. For example, one provider may supply employee count while another supplies industry.
Choose **Waterfall enrichment** in a rule or mapping to use that order. Choose a named provider to use only that provider for the field.
## Write values to your CRM
Open the connected HubSpot or Salesforce configuration and find **Enrichment mappings**.
Choose **Resolve with**, the **Normalized enrichment field**, and the CRM destination. Under **When a CRM value exists**, choose **Keep the existing value** or **Replace it**, then click **Add mapping**.
Only available enrichment values are written. Company destinations update an existing company matched by domain. Choosing a provider directly means that mapping continues to depend on that provider even if you change the waterfall order.
Disconnecting a provider preserves waterfall steps, mappings, and rule conditions. Review any **Connection required** warnings and reconnect or revise the affected configuration before relying on it.
Email validation is configured separately. See [Email verification](/integrations/email-verification.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.distro.so/integrations/enrichment.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 `automate deployments from our CI pipeline` 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.
