> ## Documentation Index > Fetch the complete documentation index at: https://docs.os.default.com/llms.txt > Use this file to discover all available pages before exploring further. # How enrichment waterfalls work in Default > How a Default enrichment waterfall uses Clearbit, Apollo, People Data Labs, and Wiza: provider order, what counts as a hit, how credits are charged, and who supplies the provider accounts. An enrichment waterfall in Default is an ordered list of up to 5 data providers that Default uses to fill in person and company fields, such as a lead's title or a company's employee count. When a provider has no answer, the next provider in the list can supply it, so a waterfall finds more data than any single provider. Default supplies the providers and bills lookups in enrichment credits. You do not need provider accounts or API keys. To build or edit a waterfall, see [Waterfalls](/settings/configurations/waterfalls). ## Enrichment waterfalls in Default at a glance | Question | Answer | | - | - | | Which providers can a waterfall use? | **Clearbit**, **Apollo**, **People Data Labs**, and **Wiza**. | | How many providers per waterfall? | Up to 5. The order you set is the priority order. | | What can it enrich? | A person from an email or a LinkedIn URL, and a company from a domain. | | Where does it run? | The **Enrich Data** workflow node, form pre-enrichment with the primary waterfall, the **Enrich** action in Tables (beta), and the Chrome extension. | | Who supplies the provider accounts? | Default. You do not need your own provider account or API key. | | How is it billed? | In enrichment credits, per provider that returns data. A miss is free, with the exceptions listed in [How enrichment credits work](#how-enrichment-credits-work). | | Can it also check emails and IP addresses? | Yes. Turn on **Email validation** or **IP validation** in the waterfall. | ## Providers you can add to a waterfall A waterfall can use 4 enrichment providers. The credits below are what Default charges when the provider returns data. The waterfall dialog shows each provider's person lookup cost next to its name. | Provider | Credits per person lookup | Credits per company lookup | Notes | | - | - | - | - | | **Clearbit** | 1 | 1 | Also charged when Clearbit finds no match. | | **Apollo** | 1 | 1 | Can enrich a person from a LinkedIn URL alone. | | **People Data Labs** | 2 | 2 | Can enrich a person from a LinkedIn URL alone. | | **Wiza** | 3 | 1 | Can enrich a person from a LinkedIn URL alone. Person lookups in a waterfall use Wiza's **Full** level, which includes email and phone. | A waterfall can also run 2 optional checks. Each check is charged every time it runs, whatever it finds: | Check | Provider | Credits per check | Needs | | - | - | - | - | | **Email validation** | **Abstract Email Reputation** | 2 | An email address | | **Email validation** | **Icypeas** | 1 | An email address | | **IP validation** | **Abstract Geolocation** | 2 | A public IP address, for example from a form submission | Icypeas verifies email addresses. It does not find them. ## Default supplies the provider data Default holds the accounts with every enrichment provider. Your workspace turns providers on and pays Default in credits: * **No provider accounts needed.** You do not need a Clearbit, Apollo, People Data Labs, or Wiza account or API key. * **Turn a provider on first.** Select **Settings** in the sidebar, then **Integrations** under **Workspace Settings**, then the **Enrichment** category, and turn the provider on. Apollo appears there as **Apollo.io (Enrichment)**, separate from the **Apollo.io (Sequencing)** card that connects your own Apollo account for sequences. The waterfall's **Add Provider** picker lists only the providers that are on. If a provider is unavailable, contact Default to turn it on for your workspace. See [Enrichment providers](/settings/integrations/enrichment). * **Credits for every provider.** Lookups from every provider are charged in the same enrichment credits. ## How Default works through the providers Default uses the waterfall's order as a priority list. How it calls the providers depends on where the waterfall runs. | Where the waterfall runs | How providers are called | Result | Providers charged | | - | - | - | - | | **Enrich Data** workflow node | All at once | Merged field by field, higher position wins | Every provider that returns data | | Form pre-enrichment (primary waterfall) | All at once | Merged field by field, higher position wins | Every provider that returns data | | **Enrich** action in Tables | One at a time, in order | The first provider that returns data | That provider | | Chrome extension | One at a time, in order | The first provider that returns data | That provider | In every case, a provider that charges for a miss, such as Clearbit, is also charged when it runs and finds nothing. ### In a workflow The **Enrich Data** node sends the lookup to every provider in the waterfall at the same time. When the answers come back, Default merges them in waterfall order: 1. Every field the provider in position 1 returned is kept. 2. The provider in position 2 fills only the fields that position 1 left empty. 3. Each later provider fills only what is still empty. For example, a waterfall lists **Apollo** first and **Wiza** second. Apollo returns a title and no phone number. Wiza returns a title and a phone number. The result takes the title from Apollo and the phone number from Wiza. Because the providers run at the same time, the node waits for the slowest provider in the waterfall. Every provider that returns data is charged, even when a higher provider already supplied most of the fields. ### Before a form is submitted Form pre-enrichment runs the workspace's **Primary Waterfall** the same way as a workflow: every provider at once, merged in waterfall order, and every provider that returns data is charged. It runs when a visitor enters an email address in a form the Pixel tracks, before they submit. See [The primary waterfall](#the-primary-waterfall). ### In Tables and the Chrome extension The **Enrich** action in Tables and **Request enrichment** in the [Chrome extension](/chrome-extension) call the providers one at a time, in waterfall order. Default stops at the first provider that returns data and uses that provider's result. Tables is in beta and turned on per workspace. ## What counts as a hit in an enrichment waterfall A provider's answer counts as a hit when all 3 of these are true: * The provider answered without an error or a timeout. * The provider did not report that it found no match. * The answer contains at least 1 field. Default also skips some lookups before they reach a provider. A skipped lookup uses no credits: | Situation | What Default does | | - | - | | The company domain comes from a personal or disposable email address, such as `gmail.com` | In a workflow, skips the company lookup and records why in the run log. **Clearbit** and **Wiza** never run company lookups on these domains. | | A person has a LinkedIn URL and no email | Calls only **Apollo**, **People Data Labs**, and **Wiza**, the providers that accept a LinkedIn URL. | | The person has neither an email nor a LinkedIn URL, or the company has no domain | Skips that lookup and records the reason. | ## How enrichment credits work Enrichment in Default is billed in credits. These rules decide what a lookup costs: * **A hit is charged.** Each provider that returns data is charged its credits for that lookup. * **A miss is free, with 2 exceptions.** Clearbit is charged when it finds no match, and email and IP validation checks are charged every time they run. * **Errors are free.** A provider error, timeout, or rate limit is never charged. * **Person and company are separate lookups.** An **Enrich Data** node with **Enrichment target** set to **Both** runs the waterfall once for the person and once for the company. * **Tests are real.** A workflow test calls the providers and uses credits. To see costs before and after a run: * **On the workflow canvas**, the **Enrich Data** node shows its maximum cost, for example `up to 4 credits`. For a waterfall, the maximum is the sum of every provider's cost, because every provider can return data. * **In the run log**, each **Enrich Data** step shows the credits it used. See [Run logs](/workflows/run-logs). * **In Tables**, the **Enrich** action shows a **Cost Breakdown** with the **Cost per record** and the **Total cost** before you run it. * **On the Waterfalls page**, each card shows the most credits the waterfall can use per lookup. ## The primary waterfall Your workspace can set 1 waterfall as its **Primary Waterfall**. Default runs the primary waterfall when a visitor types an email address into a form the Pixel tracks and leaves the field, before the form is submitted. When the form's workflow reaches an **Enrich Data** node that uses the same waterfall, the node reads the result that is already waiting instead of calling the providers again, and that lookup is not charged a second time. Email and IP validation checks are the exception: the node runs them again and they are charged again. See [Enrichment starts before the form is submitted](/enrichment/hubspot#enrichment-starts-before-the-form-is-submitted). The **Enrich Data** node itself always uses the waterfall or provider you pick in its **Enrichment source** field. Set the primary waterfall on the Waterfalls page. See [Set a waterfall as primary](/settings/configurations/waterfalls#set-a-waterfall-as-primary). ## Use a waterfall in a workflow Select **Data Model** in the sidebar, under **Configuration**, then the **Waterfalls** tab, and select **New Waterfall**. You need admin access. Add up to 5 providers under **Enrichment order** and drag them into priority order. See [Create a waterfall](/settings/configurations/waterfalls#create-a-waterfall). In **Workflows**, select **Add Node**, then choose **Enrich Data** in the **Enrichment** section. Set **Enrichment target** to **Person**, **Company**, or **Both**. Set **Enrichment source** to your waterfall, listed under **Waterfalls**. Leave **Email / Domain (optional)** empty to let Default take the email and domain from the trigger, or choose a value from an earlier node. Later nodes can pick the enriched fields from the data picker under **Person** and **Company**, for example **Title** or **Employee Count**. Write them to your CRM with an **Update Record** node, or branch on them with a **Multi-Branch** node. See [Enrichment nodes](/workflows/steps-enrichment) and [CRM nodes](/workflows/steps-crm). ## Choose the provider order Put the provider you trust most for your key fields in position 1, because its values win whenever 2 providers disagree. Then consider: * **Cost.** In a workflow, every provider that returns data is charged. A shorter waterfall costs less per record. A longer one fills more fields. * **LinkedIn URLs.** If your leads often arrive with a LinkedIn URL and no email, include **Apollo**, **People Data Labs**, or **Wiza**. * **Phone numbers.** **Wiza** returns verified emails and phone data, so it fits waterfalls that need mobile numbers. * **Email checks.** Turn on **Email validation** when a bad address would cost you, for example before adding people to a sequence. To test a waterfall, select **Test** in the workflow and then **Run Test** with a few known contacts. Then read the **Enrich Data** step in the run log. It lists each provider's attempt, whether it returned data, and the credits charged. Related: [Lead enrichment software from Default](https://www.default.com/product/lead-enrichment-software) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.