Skip to main content

What is the Enrow integration for Cargo?

Cargo is a revenue orchestration platform that lets you build enrichment workflows with full flexibility. With Cargo’s Enrow.io connector and the Enrow API, you can find professional emails, verify deliverability, and find phone numbers as part of your lead-routing and outreach automation. For Cargo’s plans, see its pricing page. Emails go through the Enrow.io connector built into Cargo. Phone numbers, and any other Enrow endpoint, go through an HTTP Request action: all Cargo plans include HTTP API access. Both use your own Enrow API key, and searches are billed in Enrow credits on your Enrow account.

How do I find and verify emails with the Enrow.io connector?

Cargo has a native Enrow.io connector with two actions:
  • Find email: finds a person’s professional email from their full name, plus the company domain or name
  • Verify email: checks whether an email address is valid
When you connect Enrow.io in Cargo, paste your Enrow API key, from the API page of the dashboard. Every workflow then reuses the connection. For the fields of each action, see Cargo’s Enrow.io documentation. The connector doesn’t find phone numbers: use an HTTP Request action for those, as described below.

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 dashboard under API. For more on how authentication works, see Authentication.

How do I add an HTTP Request action?

In your Cargo workflow, add an HTTP Request action for phone numbers, or for any Enrow endpoint the connector doesn’t cover, and configure it with the Enrow endpoint you need. You can also call the email endpoints this way. The same x-api-key header authenticates every call. Find Email:
Verify Email:
Find Phone:
For the full request and response schema of each call, see the Find Single Email, Verify Single Email, and Find Single Phone 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. Map response fields to your lead:

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: See Credits & billing for how credits are consumed across every endpoint, and 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 is the best option if you want to control your stack costs while keeping full orchestration freedom. Clay is simpler, with a table-based setup.
If you prefer the table-based approach, see the Clay integration.

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

Trigger

New lead enters from Salesforce, HubSpot, or CSV import
2

Enrich

Enrow: Find Email → Verify Email → Find Phone
3

Filter

Keep only leads with qualification: "valid" emails
4

Push

Update your CRM and trigger outreach sequences

Tips

Pass a webhook URL in your Enrow requests to get results in real-time without polling.
Use Cargo’s conditional logic to try Enrow first, then fall back to other providers if no result.
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

All Cargo plans include HTTP API access, so you can call Enrow from any plan. You authenticate with your own Enrow API key, billed separately in Enrow credits.
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.
Find email costs 1 credit per found email, verify email costs 0.25 credit per check, and find phone costs 40 credits per found phone (50 with legacy plans). See Credits & billing for the full breakdown.
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?

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.