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

# Provider support by enrichment surface

Choose a provider based on where the lookup will run. A saved chain does not guarantee identical behavior across Workflows, Records and forms.

| Surface                                 | Supported profile providers                                     | Chain behavior                                                                         |
| --------------------------------------- | --------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Workflow Enrich Lead                    | Clearbit, Apollo, People Data Labs, Wiza, Harmonic, Amplemarket | Runs configured provider intents concurrently and merges values by per-field priority. |
| Records and extension record enrichment | Apollo, Clearbit, People Data Labs, Crustdata, ZoomInfo, Ocean  | Sequential supported lookups; stops at the first usable result.                        |
| Pre-submit enrichment                   | The supported Records lookup path                               | Sequential first-hit lookup; stores early data before submission.                      |

Wiza, Harmonic and Amplemarket chain entries are skipped in the Records path. Crustdata, ZoomInfo and Ocean are not workflow Enrich Lead provider intents in the current implementation.

## Validation is separate

The supported Records path can consume chain email-check settings. Workflow Enrich Lead does not automatically execute saved chain-level email/IP switches. The IP validation switch has no automatic runtime consumer in these chain paths.

Use explicit [Abstract](/integrations/abstract.md) or [Icypeas](/integrations/icypeas.md) actions to make a workflow verification decision.

## Billing

Connections use your provider credentials and allowance. Distro does not offer a shared managed credit waterfall equivalent to a provider-bundled enrichment product.

See [Enrichment and chains](/data-and-integrations/enrichment.md) and [Pre-submit enrichment](/data-and-integrations/pre-submit.md) before reusing a chain between surfaces.


---

# 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/provider-support.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.