> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enrow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Clay Integration

> Enrich emails and phone numbers in Clay with Enrow — use the native provider or your own API key via HTTP API

Enrow is available as a native provider on <a href="https://clay.com" rel="nofollow">Clay</a>, the data orchestration platform. This guide shows you two ways to enrich contacts with Enrow inside Clay: the native provider (billed in Clay credits) and your own Enrow API key via the HTTP API enrichment (billed in Enrow credits, for more control and better pricing).

## How do I use Enrow as a native Clay provider?

The fastest way to get started is the native Enrow provider built into Clay. You can run it directly from your Clay tables using your Clay credits — no API key setup required:

| Action           | Clay Credits         |
| ---------------- | -------------------- |
| **Find email**   | 0.2 per find         |
| **Verify email** | 0.1 per verification |
| **Find phone**   | 20 per phone         |

The native provider covers Enrow's core actions — [Email Finder](/api-reference/email-finder/find-single), [Email Verifier](/api-reference/email-verifier/verify-single), and [Phone Finder](/api-reference/phone/find-single).

## How do I use my own Enrow API key in Clay?

For more control and better pricing, use your own Enrow API key directly in Clay via the **HTTP API** enrichment. This requires a Clay **Growth plan** (starting at $495/mo monthly, $446/mo annually — <a href="https://clay.com/pricing" rel="nofollow">see pricing</a>) which gives you access to HTTP API actions.

Authenticate every request with your API key in the `x-api-key` header — see [Authentication](/authentication) for how to find your key.

### How do I set up the HTTP API enrichment?

Configure an HTTP API enrichment that calls the Enrow [Find Single Email](/api-reference/email-finder/find-single) endpoint:

1. Open your Clay table
2. Click **"Add Enrichment"** → search for **"HTTP API"**
3. Configure the request:

```
Method: POST
URL: https://api.enrow.io/email/find/single

Headers:
  x-api-key: YOUR_ENROW_API_KEY
  Content-Type: application/json

Body:
{
  "company_domain": /company_domain,
  "fullname": "/first_name /last_name"
}
```

<Note>
  In Clay, use `/column_name` to reference columns from your table.
</Note>

### How do I retrieve the enrichment results?

The Enrow API is asynchronous — the POST request returns a search ID, and the result is delivered separately. There are two ways to get the result back into Clay:

**Option A: Webhooks (Recommended)**

Add a webhook URL in your request so Enrow notifies Clay automatically once the search finishes. See [How webhooks work](/how-webhooks-work) for the notification format:

```json theme={null}
{
  "company_domain": /company_domain,
  "fullname": "/first_name /last_name",
  "settings": {
    "webhook": "YOUR_CLAY_WEBHOOK_URL"
  }
}
```

**Option B: Delay + GET**

1. Add a **Delay** step (5-10 seconds)
2. Add another HTTP API step to fetch the result with the search ID via the [Get Single Result](/api-reference/email-finder/get-single-result) endpoint:

```
Method: GET
URL: https://api.enrow.io/email/find/single?id={id}
Headers:
  x-api-key: YOUR_ENROW_API_KEY
```

## Which Enrow endpoints can I call from Clay?

When using your own API key, you can call any Enrow endpoint from the HTTP API enrichment. The most common ones and their costs in Enrow credits are below — see [Credits & billing](/credits-billing) for the full per-endpoint breakdown:

| Action       | Endpoint                    | Enrow Credits  |
| ------------ | --------------------------- | -------------- |
| Find email   | `POST /email/find/single`   | 1 per found    |
| Verify email | `POST /email/verify/single` | 0.25 per check |
| Find phone   | `POST /phone/single`        | 50 per found   |

## What are the alternatives to Clay?

If Clay's pricing or table-based model doesn't fit your stack, two alternatives let you run Enrow enrichment with more flexibility:

<AccordionGroup>
  <Accordion title="Cargo — Starting at $250/mo">
    <a href="https://getcargo.ai" rel="nofollow">Cargo</a> is a more affordable alternative starting at \$250/mo. It's less restrictive and gives you more freedom in orchestration, making it a great option if you want to control your stack costs. The tradeoff is that it's a bit more technical than Clay's drag-and-drop tables.

    [See the Cargo integration guide →](/integrations/orchestrators/cargo)
  </Accordion>

  <Accordion title="Build It Yourself with Claude">
    The most flexible and cost-effective option is to build your own enrichment workflows using the Enrow API directly. Use our [llms-full.txt](https://docs.enrow.io/llms-full.txt) with Claude or any LLM to generate integration code in minutes.
  </Accordion>
</AccordionGroup>

## How do I get the most out of Enrow in Clay?

Follow these practices to save credits and maximize deliverability:

<AccordionGroup>
  <Accordion title="Filter Before Enriching">
    Only enrich contacts that are missing data — filter by decision makers, target companies, or contacts without emails. This saves credits.
  </Accordion>

  <Accordion title="Use Waterfall Logic">
    Set up Enrow as your primary source, then fall back to other providers using Clay's **"Run if"** conditions.
  </Accordion>

  <Accordion title="Always Verify">
    Even with Enrow's determinist verification, run a verification step before campaigns for maximum deliverability.
  </Accordion>
</AccordionGroup>

## Why is my Clay enrichment failing?

Most issues come from authentication or input data. Here are the most common problems and fixes:

**"Unauthorized" Error**

* Check your API key is correct
* Verify it's in the `x-api-key` header (not `Authorization`)

A `401 Unauthorized` response means the API key is missing or invalid — see [Status codes](/status-codes) and [Error handling](/error-handling) for the full list of responses.

**No Results Returned**

* Check that the company domain is valid
* Try with `company_name` instead
* Some contacts may genuinely not have findable emails

## FAQ

<AccordionGroup>
  <Accordion title="Should I use the native provider or my own API key?">
    Use the native Enrow provider for the quickest setup and to keep everything billed in Clay credits. Use your own Enrow API key via the HTTP API enrichment when you want more control and better pricing — this requires a Clay Growth plan.
  </Accordion>

  <Accordion title="Why does the POST request only return a search ID?">
    The Enrow API is asynchronous, so the POST request starts the search and returns an `id`. Retrieve the result with a [webhook](/how-webhooks-work) or by calling the [Get Single Result](/api-reference/email-finder/get-single-result) endpoint with that `id`.
  </Accordion>

  <Accordion title="How many credits does each action cost?">
    With the native provider, a find email costs 0.2 Clay credits, a verify email costs 0.1, and a find phone costs 20. With your own API key, the same actions cost 1, 0.25, and 50 Enrow credits respectively. See [Credits & billing](/credits-billing) for details.
  </Accordion>

  <Accordion title="Do I still need to verify emails found by Enrow?">
    Enrow runs determinist verification on found emails, including catch-all addresses. For maximum deliverability before a campaign, you can still add a dedicated [Email Verifier](/api-reference/email-verifier/verify-single) step.
  </Accordion>
</AccordionGroup>

## Need help?

* **Clay Documentation**: <a href="https://clay.com/docs" rel="nofollow">clay.com/docs</a>
* **Enrow API Docs**: [API Overview](/api-overview)
* **Support**: [api@enrow.io](mailto:api@enrow.io)

## Next steps

<CardGroup cols={2}>
  <Card title="Find an email" icon="envelope" href="/api-reference/email-finder/find-single">
    See the endpoint Clay calls to find a professional email address.
  </Card>

  <Card title="Webhooks" icon="bell" href="/how-webhooks-work">
    Get results pushed back to Clay automatically when a search completes.
  </Card>

  <Card title="Cargo integration" icon="diagram-project" href="/integrations/orchestrators/cargo">
    Run Enrow enrichment in a more flexible orchestrator.
  </Card>

  <Card title="Credits & billing" icon="coins" href="/credits-billing">
    See how credits are consumed for each endpoint.
  </Card>
</CardGroup>