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

# Enrow.io

> Connect Enrow.io to find and verify email addresses in your workflows.

## How to set up Enrow\.io

### Authentication

Enrow\.io uses API key authentication:

1. Sign up at [enrow.io](https://enrow.io)
2. Navigate to your API settings
3. Copy your API key
4. Paste the API key in Cargo when connecting

## Enrow\.io actions

### Find email

Find a person's email address using their name and company.

**Required fields:**

* **Full name**: Person's full name

**Optional fields:**

* **Company domain**: Company's domain (e.g., "apple.com" or "[https://www.apple.com](https://www.apple.com)")
* **Company name**: Company's name (e.g., "Apple", "Air France")
* **Country code**: ISO 3166 Alpha-2 country code (helps when using company name)

**Credits:** 1 credit per request

**Use case:** Discover professional email addresses for prospecting.

### Verify email

Check if an email address is valid and deliverable.

**Required fields:**

* **Email**: The email address to verify

**Optional fields:**

* **Country code**: ISO 3166 Alpha-2 country code

**Credits:** 0.1 credits per request

**Use case:** Validate emails before sending campaigns.

## Credits summary

| Action       | Credits |
| ------------ | ------- |
| Find email   | 1       |
| Verify email | 0.1     |

## Retry behavior

Enrow\.io actions include automatic retry logic:

* Maximum 8 retry attempts
* Exponential backoff (starting at 2 seconds)
* Handles rate limits automatically

## Rate limits

Enrow\.io API has a rate limit of 60 requests per minute. Cargo handles rate limiting automatically.

## Best practices

* Provide company domain for best email finding accuracy
* Use country code when using company name instead of domain
* Always verify found emails before outreach (very affordable at 0.1 credits)
* Combine find + verify for complete validation
* Cache results to avoid redundant lookups
