> ## 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.

# Cargo Integration

> Connect Enrow to Cargo to enrich and verify leads with email, verification, and phone data inside your revenue orchestration workflows

## What is the Enrow integration for Cargo?

<a href="https://getcargo.ai" rel="nofollow">Cargo</a> is a revenue orchestration platform that lets you build enrichment workflows with full flexibility. By calling the Enrow API from a Cargo workflow, you can find professional emails, verify deliverability, and find phone numbers as part of your lead-routing and outreach automation. Plans start at **\$250/mo** (<a href="https://getcargo.ai/pricing" rel="nofollow">see pricing</a>).

You can use your Enrow API key directly in Cargo — all plans include HTTP API access. This gives you full control over your enrichment stack at the best cost. Every request authenticates with your [API key](/authentication) in the `x-api-key` header.

## How do I store my Enrow API key in Cargo?

Store your Enrow API key as a Cargo secret so it can be referenced by every HTTP Request action without hardcoding it:

1. In Cargo, go to **Secrets**
2. Add a new secret: `ENROW_API_KEY` with your key

You can find your API key in the [app.enrow.io](https://app.enrow.io) dashboard under **API**. For more on how authentication works, see [Authentication](/authentication).

## How do I add an HTTP Request action?

In your Cargo workflow, add an **HTTP Request** action and configure it with the Enrow endpoint you need. The same `x-api-key` header authenticates every call.

**Find Email:**

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

Headers:
  x-api-key: {{secrets.ENROW_API_KEY}}
  Content-Type: application/json

Body:
{
  "company_domain": "{{lead.company_domain}}",
  "fullname": "{{lead.first_name}} {{lead.last_name}}",
  "settings": {
    "webhook": "{{cargo.webhook_url}}"
  }
}
```

**Verify Email:**

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

Headers:
  x-api-key: {{secrets.ENROW_API_KEY}}
  Content-Type: application/json

Body:
{
  "email": "{{lead.email}}"
}
```

**Find Phone:**

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

Headers:
  x-api-key: {{secrets.ENROW_API_KEY}}
  Content-Type: application/json

Body:
{
  "linkedin_url": "{{lead.linkedin_url}}"
}
```

For the full request and response schema of each call, see the [Find Single Email](/api-reference/email-finder/find-single), [Verify Single Email](/api-reference/email-verifier/verify-single), and [Find Single Phone](/api-reference/phone/find-single) references.

## How do I handle the results?

Enrow searches run asynchronously, so the initial response returns an `id` rather than the final result. Use a **Webhook Listener** in your workflow to receive Enrow results, or add a Delay + GET step to poll for results. Passing a webhook URL is the faster option — see [How webhooks work](/how-webhooks-work).

Map response fields to your lead:

| Enrow Field     | Lead Field          |
| --------------- | ------------------- |
| `email`         | Email               |
| `qualification` | Email Qualification |
| `phone`         | Phone               |
| `country_code`  | Phone Country       |

## Which endpoints can I call from Cargo?

These are the single-search Enrow endpoints most commonly used in Cargo workflows, along with their credit cost:

| 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   |

See [Credits & billing](/credits-billing) for how credits are consumed across every endpoint, and [Rate limits](/rate-limits) before scaling up large workflows.

## Should I use Cargo or Clay?

Use Cargo if you want to control your stack costs while keeping full orchestration freedom; use Clay if you prefer a simpler, table-based setup. The table below compares the two:

|                     | Cargo                       | Clay                      |
| ------------------- | --------------------------- | ------------------------- |
| **Starting price**  | \$250/mo                    | \$495/mo (for API access) |
| **HTTP API access** | All plans                   | Growth plan only          |
| **Flexibility**     | Full workflow orchestration | Table-based, simpler      |
| **Learning curve**  | More technical              | Easier drag-and-drop      |

<Info>
  Cargo is the best option if you want to control your stack costs while keeping full orchestration freedom. Clay is simpler but more restrictive and more expensive for API usage.
</Info>

If you prefer the table-based approach, see the [Clay integration](/integrations/orchestrators/clay).

## What does a full enrichment workflow look like?

A typical Cargo workflow enriches a new lead end to end, filters on email quality, then pushes the result to your CRM:

<Steps>
  <Step title="Trigger">
    New lead enters from Salesforce, HubSpot, or CSV import
  </Step>

  <Step title="Enrich">
    Enrow: Find Email → Verify Email → Find Phone
  </Step>

  <Step title="Filter">
    Keep only leads with `qualification: "valid"` emails
  </Step>

  <Step title="Push">
    Update your CRM and trigger outreach sequences
  </Step>
</Steps>

## Tips

<AccordionGroup>
  <Accordion title="Use Webhooks for Speed">
    Pass a webhook URL in your Enrow requests to get results in real-time without polling.
  </Accordion>

  <Accordion title="Build a Waterfall">
    Use Cargo's conditional logic to try Enrow first, then fall back to other providers if no result.
  </Accordion>

  <Accordion title="Bulk for Large Lists">
    For 100+ contacts, use the bulk endpoints (`/email/find/bulk`, `/email/verify/bulk`, `/phone/bulk`) for better performance.
  </Accordion>
</AccordionGroup>

## Can I build my own integration instead?

Yes. If you want even more control, call the Enrow API directly in your own code. Our [llms-full.txt](https://docs.enrow.io/llms-full.txt) makes it easy to generate integration code with Claude or any LLM in minutes.

## FAQ

<AccordionGroup>
  <Accordion title="Do I need a paid Cargo plan to use Enrow?">
    All Cargo plans include HTTP API access, so you can call Enrow from any plan. Cargo pricing starts at \$250/mo. You authenticate with your own Enrow API key, billed separately in Enrow credits.
  </Accordion>

  <Accordion title="Why does the Find Email response not contain the email?">
    Enrow searches run asynchronously. The initial response returns an `id`, and the final result arrives via your webhook or a GET poll. Use a Webhook Listener for real-time results — see [How webhooks work](/how-webhooks-work).
  </Accordion>

  <Accordion title="How many credits does each action cost?">
    Find email costs 1 credit per found email, verify email costs 0.25 credit per check, and find phone costs 50 credits per found phone. See [Credits & billing](/credits-billing) for the full breakdown.
  </Accordion>

  <Accordion title="My request returns a 401 error — what's wrong?">
    A `401` means the `x-api-key` header is missing or invalid. Confirm the `ENROW_API_KEY` secret holds a valid key and is referenced as `{{secrets.ENROW_API_KEY}}`. See [Error handling](/error-handling) and [Status codes](/status-codes) for details.
  </Accordion>
</AccordionGroup>

## Need Help?

* **Cargo Documentation**: <a href="https://getcargo.ai/docs" rel="nofollow">getcargo.ai/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">
    Search for a professional email address from a name and company.
  </Card>

  <Card title="Webhooks" icon="bell" href="/how-webhooks-work">
    Get notified automatically when a search completes.
  </Card>

  <Card title="Clay integration" icon="layer-group" href="/integrations/orchestrators/clay">
    Compare the table-based alternative for enrichment workflows.
  </Card>

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