What is the Enrow integration for Cargo?
Cargo 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 (see pricing). 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 in thex-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:- In Cargo, go to Secrets
- Add a new secret:
ENROW_API_KEYwith your key
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 samex-api-key header authenticates every call.
Find Email:
How do I handle the results?
Enrow searches run asynchronously, so the initial response returns anid 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.
Map response fields to your lead:
| Enrow Field | Lead Field |
|---|---|
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 |
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 |
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.
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:Tips
Use Webhooks for Speed
Use Webhooks for Speed
Pass a webhook URL in your Enrow requests to get results in real-time without polling.
Build a Waterfall
Build a Waterfall
Use Cargo’s conditional logic to try Enrow first, then fall back to other providers if no result.
Bulk for Large Lists
Bulk for Large Lists
For 100+ contacts, use the bulk endpoints (
/email/find/bulk, /email/verify/bulk, /phone/bulk) for better performance.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 makes it easy to generate integration code with Claude or any LLM in minutes.FAQ
Do I need a paid Cargo plan to use Enrow?
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.
Why does the Find Email response not contain the email?
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 many credits does each action cost?
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 for the full breakdown.
My request returns a 401 error — what's wrong?
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 and Status codes for details.Need Help?
- Cargo Documentation: getcargo.ai/docs
- Enrow API Docs: API Overview
- Support: api@enrow.io
Next steps
Find an email
Search for a professional email address from a name and company.
Webhooks
Get notified automatically when a search completes.
Clay integration
Compare the table-based alternative for enrichment workflows.
Credits & billing
See how credits are consumed for each endpoint.

