Integrations
Lusha
B2B email + direct-dial enrichment with strong NA/EU coverage. LinkedIn /in/ URLs only — no Sales Navigator.
Use Lusha for B2B email and direct-dial enrichment when mobile/desk numbers matter. Strong North American and European coverage, plus intent signals. It often surfaces direct dials other providers miss.
Managed credits or BYOK. Email and phone are separate methods with separate prices: an email reveal bills 2.8–2.9 credits per result, a phone reveal 13.8–13.9 (a phone costs five times an email on Lusha's side). Enrich (company) is a flat 2.8; search-contact results bill 2.8 credits per request; get_usage is free.
Capabilities
| Tool | Does | Cost |
|---|---|---|
enrich_person_email | Email from LinkedIn URL, email, or name+company | 2.9 cr / result |
enrich_person_phone | Direct dial from the same identifiers | 13.9 cr / result |
enrich_company | Size, revenue, industry, technologies from a domain | 2.8 cr / result |
search_contacts | Prospecting search (seniority, dept, size, industry, title) | 2.8 cr / request |
enrich_contact_emails | Reveal emails for ids from a search | 2.8 cr / result |
enrich_contact_phones | Reveal phones for ids from a search | 13.8 cr / result |
get_usage | Balance / usage / catalog | Free |
Guidance
- Best input is a
linkedin.com/in/URL; email orfirst_name+last_name+(company_nameorcompany_domain) also work. Sales Navigator / Recruiter URLs fail. - Never pass a name alone —
company_namewithoutfirst_name+last_namewon't resolve. - For company enrich, send a bare domain (no
http://, nowww.). - Phones: read the
phones[]array first; top-levelphoneisn't always populated. - The method fixes the field, and the price. Call an
*_emailmethod for an email and a*_phonemethod for a direct dial — there is no field argument, so an email-only play can never be billed the phone rate. Reach for a phone method only when the play needs to dial.
hyreflow tools execute lusha enrich_person_email \
--payload '{"linkedin_url":"https://www.linkedin.com/in/johndoe"}'In a waterfall: member of the email_enrichment chain (see Integrations Overview).