Leads Finder — B2B Leads with Emails by Title, Industry, Tech ✅ avatar

Leads Finder — B2B Leads with Emails by Title, Industry, Tech ✅

Pricing

from $2.00 / 1,000 results

Go to Apify Store
Leads Finder — B2B Leads with Emails by Title, Industry, Tech ✅

Leads Finder — B2B Leads with Emails by Title, Industry, Tech ✅

Find B2B leads with work emails by job title, seniority, department, location, company, industry, tech stack, funding, traffic and hiring. 10–100 leads per run with LinkedIn URL, title, company and firmographics. No cookies or account required.

Pricing

from $2.00 / 1,000 results

Rating

5.0

(1)

Developer

NeuralVerge

NeuralVerge

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

2 days ago

Last modified

Share

Leads Finder — B2B Leads with Emails ✅ No Cookies

Find B2B leads across a database of hundreds of millions of professional profiles, filtered by job title, seniority, department, location, company, industry, tech stack, funding, website traffic, hiring signals and HQ location. Get name, title, seniority, department, location, LinkedIn URL and the employer's firmographics per person. Powered by the Neuralverge API. No cookies or account required.

Ideal for outbound sales prospecting, ABM lists, recruiting and market mapping.

✨ Why this Actor

  • 🎯 70+ filters in one search — person, location, company, NAICS / SIC / LinkedIn industry, CRM / cloud / ERP and other tech, funding stage and amount, traffic, team headcount and open roles, HQ — combine any of them.
  • 🏢 Firmographics on every row — company name, domain, LinkedIn URL, headcount, industry, revenue band, founding year, HQ, funding and traffic, no second lookup needed.
  • 📇 Clean lead table — one row per person, ready for a spreadsheet, CRM, sequencer or AI pipeline.
  • 🍪 No cookies, login or account — never share LinkedIn credentials or risk account restrictions. Everything runs on the Neuralverge backend.
  • 📧 Find email — switch on findEmail to get each lead's work email from their name and company domain, $10 per 1,000 results.
  • 📄 Deep paging — walk a big search page by page (up to 500,000 pages of 10–100 leads) without paying twice for the same people.
  • 💳 Simple pricing — $2 per 1,000 results ($0.002 each, one result = one lead). A search that matches nobody returns a single no result row and costs $0.002. A run that fails is never charged.

🔧 How it works

  1. Pick your filters — e.g. jobTitles: ["Head of Sales"] + countries: ["Germany"]. Optionally restrict to one company with companyLinkedinUrl.
  2. Choose the page size — pageSize from 10 to 100 leads, and page to continue further down the list.
  3. Run the Actor. You get one dataset row per lead — or a single no result row if the filters matched nobody. The run log shows how many people match in total and how many pages there are. Export to CSV, JSON or Excel, or pull it over the Apify API.

Input

At least one filter or a companyLinkedinUrl is required.

The input form has the same tabs and filters as Neuralverge's own Leads search page.

TabFields
—pageSize (Leads per page, 10–100, default 25), page (up to 500,000, default 1), findEmail (default false)
PersonfirstName, lastName, personHeadline / excludePersonHeadline (Headline), jobTitles / excludeJobTitles (Job Title, contains match), seniorityLevels (C-Level, VP, Director, Manager, Staff, Other), departments (22 departments), skills, languages
Locationcountries, continents, states (State / Province), cities
CompanycompanyLinkedinUrl (search only inside this company), companyNames (+ companyNameFuzzy), companyHeadline / excludeCompanyHeadline, companyOverview / excludeCompanyOverview, domains / excludeDomains, employeesMin / employeesMax, revenue
IndustrynaicsIndustries (NAICS), sicIndustries (SIC)
LinkedInlinkedinIndustries
Tech Stackcrm, salesAutomation, marketingAutomation, analytics, cms, cloudProvider, development, ecommerce, erp, emailHosting, emailSecurity, appSecurity, cloudSecurity, abm, conversationIntelligence
FundingfundingTypes, minTotalFunding, minLastFunding, leadInvestors, minInvestors
Traffic & GrowthminTotalTraffic, minOrganicTraffic, minPaidTraffic, minAdSpend, minLinkedinGrowth (all ≥)
HiringTeam headcount ≥ minEngineeringHeadcount, minSalesHeadcount, minMarketingHeadcount; open roles ≥ minSalesOpenRoles, minEngineeringOpenRoles, minMarketingOpenRoles, minItOpenRoles, minDevopsOpenRoles
Company AttributeshasMobileApp, hasWebApp, hasCiso, hasCio — yes / no
HQ LocationhqCountries, hqCities, hqState
{
"jobTitles": ["Head of Sales"],
"countries": ["Germany"],
"pageSize": 25,
"page": 1
}

What you'll receive

One dataset row per lead:

  • Person — ranking, fullName, firstName, lastName, headline, linkedinUrl, jobTitle, seniorityLevel, department, skills
  • Email (with findEmail) — email, emailStatus (found / not_found / no_domain / no_name / error), emailConfidence — right after linkedinUrl
  • Location — location, city, state, country
  • Company — company, companyLinkedinUrl, companyDomain, emailDomain, companyEmployeeCount, companyIndustry, companyRevenue, companyFoundedOn, companyHq
  • Signals — companyTotalFunding, companyLastFundingType, companyLastFundingDate, companyMonthlyTraffic, companyLinkedinGrowthRate

Nulls are normal. Only fields known for the person or company are filled. ranking is the lead's position in the whole result list, so rows from different pages never collide.

Example output (real run)

One lead from a search for jobTitles: ["Head of Sales"], countries: ["Germany"]:

{
"ranking": 1,
"fullName": "Anna Heller",
"firstName": "Anna",
"lastName": "Heller",
"headline": "head of sales operations jokey group",
"linkedinUrl": "https://www.linkedin.com/in/anna-heller-5739652a3",
"location": "Germany",
"city": null,
"state": null,
"country": "Germany",
"emailDomain": "jokey.com",
"jobTitle": "Head of Sales Operations Jokey Group",
"seniorityLevel": "Other",
"department": "Other",
"skills": [],
"company": "Jokey Group",
"companyLinkedinUrl": "https://www.linkedin.com/company/jokey-group",
"companyDomain": "jokey.com",
"companyEmployeeCount": 745,
"companyIndustry": "Offices of Other Holding Companies;All Other Plastics Product Manufacturing;Other Chemical and Allied Products Merchant Wholesalers",
"companyRevenue": "$10M to <$50M",
"companyFoundedOn": "1968",
"companyHq": "Wipperfürth, Germany",
"companyTotalFunding": 0,
"companyLastFundingType": null,
"companyLastFundingDate": null,
"companyMonthlyTraffic": 41,
"companyLinkedinGrowthRate": 2
}

Genuine output from a live run — one of 10,305 leads matching this search.

When nothing is found

A search that runs but matches nobody still returns a row, so a batch never silently loses an input:

ColumnValue
companyLinkedinUrlthe company you submitted, or null
pagethe page you asked for
foundfalse
messagewhy nothing was returned

Filter these out with found != false. This row is billed as one result — see Pricing.

Pricing — pay per event

This Actor uses Apify Pay-Per-Event:

EventPriceCharged
Actor startfreenever
Result (one lead = one dataset row)$2 per 1,000 results ($0.002 each)every lead, including the no result row
Email lookup result$10 per 1,000 results ($0.01 each)only with findEmail — every lookup that runs, email found or not

A run that returns 25 leads costs 25 × $0.002 = $0.05; 1,000 leads cost $2.00. With findEmail, 25 leads cost 25 × ($0.002 + $0.01) = $0.30; a lead without a company domain is not looked up and not charged for the email.

A completed search is billed even when it matches nobody — it writes one explicit no result row (found: false and a message), so it costs $0.002. A run that fails (missing input, bad key, upstream error) writes no row; and is not charged.

Rate limit

There is a ceiling on how fast one Apify account can pull from the Neuralverge backend: 5 requests per second across the Neuralverge Actors. One run is one request, so this is about how many runs you start at once, not about the size of a single run.

Above the ceiling the backend answers HTTP 429. The Actor waits out the Retry-After it asks for and retries a few times before giving up; a run that does give up writes no row and is not charged.

If you need a higher rate for a bulk job, get in touch.

Free plan limits

Users on any paid Apify plan are not affected by anything in this section.

On the Apify Free plan this Actor may be started 3 times per calendar month per user. A run that finds nothing still counts, because the search is performed either way. Every Neuralverge Actor carries its own allowance — running one never uses up another's.

In addition, on the Free plan:

  • a run returns at most 25 leads;
  • Find email is unavailable — such a run continues without emails and says so in the log.

When a limit is reached the Actor stops gracefully with a status message naming it; everything resets on the 1st of every month, and any paid Apify plan removes all of it.

Pricing is on top of your Apify platform usage.

Integrations & API

Results are stored in a standard Apify dataset — export as CSV, JSON, XML or Excel, or fetch on demand through the Apify API. The Actor also plugs into Apify's integrations (Make, Zapier, n8n, webhooks) and can be called from any MCP client.

FAQ

Do I need a LinkedIn account or cookies? No. Everything runs on the Neuralverge backend — you never provide credentials or a session.

How do I get more than 100 leads? Run again with page: 2, 3, … — the run log tells you how many pages the search has. Each page is new people, so you never pay twice.

How do I get emails? Switch on findEmail — each lead gets a work email looked up from its name and company domain ($10 per 1,000 results).

What is the difference from LinkedIn People Search? This Actor searches a B2B database with company-level signals (tech stack, funding, traffic, hiring) and returns firmographics on every row. LinkedIn People Search queries LinkedIn's own people search.

🔗 Other Neuralverge Actors


Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn® is a registered trademark of LinkedIn Corporation. All trademarks are property of their respective owners.