Enrow + Cargo

Overview

What you can do

• Find work emails

  Automatic1 credit if found

  The connector's Find email action takes a full name, plus a company domain or name, and returns the lead's work email, verified.

• Verify emails

  Automatic0.25 credit per check

  Verify email checks an address before it reaches a sequence, catch-all addresses included.

• Find phone numbers

  Automatic40 credits if found

  An HTTP call to Enrow's phone endpoint, with the lead's LinkedIn URL, returns their phone number.

• Keep only valid emails

  Automatic

  A Branch node reads the qualification Enrow returns and sends only valid emails on to your CRM or sequence.

• Get results by webhook

  Automatic

  For HTTP calls, a Listen webhook gives you a URL to pass in settings.webhook: each result lands there when its search ends.

How to set it up

1. 01

   Connect Enrow.io

   In Cargo, add the Enrow.io connector and paste your Enrow API key, from the Enrow app. The Find email and Verify email actions are then available in your workflows.

2. 02

   Add the phone call

   For phone numbers, add the HTTP connector with your key as a secret x-api-key header, then a Call action to the phone endpoint, as below.

3. 03

   Build the workflow

   A typical play: a new lead lands in your CRM, Enrow finds and verifies the email and finds the phone, a Branch node keeps valid emails, and the lead goes back to the CRM or into a sequence.

POST https://api.enrow.io/phone/single
x-api-key: YOUR_ENROW_API_KEY
Content-Type: application/json

{
  "linkedin_url": "{{nodes.start.linkedin_url}}",
  "settings": { "webhook": "YOUR_CARGO_WEBHOOK_URL" }
}

Good to know

• →The Enrow.io connector covers emails only, finding and verifying. Phone numbers go through an HTTP call with the same API key.
• →An HTTP call to Enrow returns a search id, not the result: the API is asynchronous. Get the result with a Listen webhook, or a Delay node followed by a GET with that id.
• →Store your key as a secret header in the HTTP connector, never in plain text inside a node.
• →A search that finds nothing costs no Enrow credits, so you can try Enrow first and branch to another provider only when nothing comes back.
• →For large lists, Enrow's bulk endpoints take up to 5,000 searches per request, at the same price per result.

Questions

Resources

• Setup guideHow to connect Cargo to Enrow
• ProductThe Enrow API
• ProductEnrow Direct Phone Finder
• ArticleEmail Finder API: The Four Things the Docs Don't Tell You