> 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/data-and-integrations/enrichment.md). # Enrichment and chains Enrichment fills person or company details from connected data providers. Use it before qualification or routing when your form does not collect everything the decision needs. ## Connect a provider Connect the provider in workspace integration settings and review its permitted enrichment scope. Workflow Enrich Lead providers include **Clearbit**, **Apollo**, **People Data Labs**, **Wiza**, **Harmonic**, and **Amplemarket**. Some connections allow company enrichment only. Person enrichment needs a provider and connection that support it. ## Create a chain Open **Field catalog → Enrichment chains** and create a chain. Name it after the job it does, add up to five distinct providers, and arrange **Provider order**. Position 1 has the highest priority. Workflow Enrich Lead runs configured provider intents concurrently and merges the higher-priority usable value for each field. Records and pre-submit enrichment use a different, sequential first-hit path and a different supported provider list. See [Provider support by surface](/data-and-integrations/provider-support.md). Choose a primary chain if workflows should use a workspace default. ## Add Enrich Lead In the workflow, add **Enrich Lead** and select: * **What to enrich**: Person, Company, or Person and company. * **Source**: Enrichment chain or Single provider. * The chain or provider. * **Email / Domain**, or the current lead identity when available. * An optional LinkedIn URL for supported providers. Use its outputs in later Branch, rulebook, CRM, or message steps. ## Handle missing data A successful lookup can still return no match or only some fields. Check status and the required values before routing. For example, if company size is unavailable, use a known form answer or a separate follow-up path. Do not treat a missing value as confirmed disqualification. Provider failure is a separate case. Inspect the delivery error and follow your recovery process. ## Publication and provider usage Publishing retains the Enrich Lead policy for that workflow version. After changing a chain, republish the workflow when you want it to adopt the new policy. Real enrichment uses your connected provider account and may consume its usage or credits. Use samples for simulation and controlled identifiers for live checks. Workflow Enrich Lead does not automatically execute saved chain email/IP validation flags. Use explicit [Abstract](/integrations/abstract.md) or [Icypeas](/integrations/icypeas.md) actions for a workflow validation decision. The chain IP switch has no automatic runtime consumer in these paths. See [Pre-submit enrichment](/data-and-integrations/pre-submit.md) before enabling an early form lookup; a later workflow enrichment step makes separate calls. --- # 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/data-and-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 `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.