LinkedIn B2B Emails Scraper: Verified Email Finder

LinkedIn B2B Email Scraper — Extract Emails, Domains and Companies

LinkedIn B2B Emails Scraper: Verified Email Finder searches Google for public LinkedIn content and returns business email addresses along with their resolved domain, company name, and B2B-vs-personal classification. Every lead — email, domain, company, keyword, and source url — is delivered as structured JSON, ready to import into a CRM or outreach tool without any parsing. Configure your keywords and domain allowlist, then run it directly on Apify to start collecting leads.

What is LinkedIn B2B Emails Scraper: Verified Email Finder?

LinkedIn B2B Emails Scraper: Verified Email Finder is an Apify Actor that discovers publicly indexed LinkedIn business emails by running targeted Google searches, then classifies each result as corporate or personal and optionally restricts output to a company-domain allowlist. It requires no LinkedIn account, login, or session cookies — every request goes to Google's public search results, never to LinkedIn itself. It's built for sales development reps, growth marketers, and lead-generation teams who need a keyword-driven way to build outreach lists without manually searching LinkedIn one page at a time.

What LinkedIn B2B email data is publicly available to scrape?

This Actor never logs into LinkedIn — it only reads what Google has indexed from LinkedIn's public pages.

Data category	Publicly available (Google-indexed)	Restricted (LinkedIn login)
Title & snippet from a public page	Yes	—
Email in a public bio or contact section	Yes, if posted	—
Source LinkedIn URL	Yes	—
Full work history & complete profile text	Snippet only	Needs login
Connections, followers, InMail	No	Login (+ Premium)
Inbox deliverability confirmation	Not available anywhere	Not exposed anywhere

It only returns publicly visible data already indexed by Google — nothing behind a login wall.

What data can I extract with LinkedIn B2B Emails Scraper: Verified Email Finder?

LinkedIn B2B Emails Scraper: Verified Email Finder returns one flat JSON row per discovered email, covering lead identity, search/classification metadata, and result context.

Field	Description
email	The discovered email address, extracted from a public Google search result snippet.
domain	Domain portion of the email, resolved by the Actor (e.g. brightpeakmarketing.com).
company	Best-effort human-readable company name derived from the domain.
url	Source LinkedIn page URL where the email was found.
keyword	The search keyword that produced this result.
pattern	Name of the B2B search-pattern template that surfaced this email (corporate mode only; empty in personal mode).
leadType	Classification of the email as b2b (corporate) or personal.
network	Platform searched — currently always LinkedIn.com.
location	Geographic filter applied to the search, if any.
title	Title of the Google search result page.
description	Snippet/description text from the Google search result.
scraped_at	UTC timestamp when the row was collected.

Email, domain and company identity

email, domain, company, url — the core lead: who to contact, at what company, and where the mention was found.

Search and classification metadata

keyword, pattern, leadType, network, location — how the lead was found and how it was classified.

Result context

title, description, scraped_at — the surrounding Google result text and when the row was collected.

🤖 Add-on: Need additional LinkedIn data?

Pair this Actor with LinkedIn Company Scraper & Open Jobs Finder to pull firmographics and open-jobs signals for the companies behind the domains you collect, or with LinkedIn Company Employees : AI & Lead Enrichment Scraper to enrich a company's employee list with sentiment and lead-scoring data. For individual outreach targets, LinkedIn Profile & Credibility Analysis Scraper adds a per-profile credibility read before you send that first email.

How does LinkedIn B2B Emails Scraper: Verified Email Finder differ from the official LinkedIn API?

LinkedIn does not offer a public, self-serve API for discovering business emails: its official APIs (the Marketing Developer Platform and Talent Solutions APIs) are restricted to approved Partner Program members and scoped to specific use cases like ads management or job-board syndication — not general profile or company search.

Feature	LinkedIn official API	LinkedIn B2B Emails Scraper: Verified Email Finder
Access model	Partner Program application and approval required	Runs immediately on Apify — no LinkedIn approval needed
Email discovery	Not exposed as a capability at all	Purpose-built: keyword- and pattern-driven email discovery
Data scope	Limited to LinkedIn assets you already own or manage	Any public LinkedIn content already indexed by Google matching your keywords
Setup time	Application, review, and approval process before any access	Configure input fields and start a run
Company-domain filtering	Not a built-in concept	Native allowedDomains allowlist, enforced in every mode
Third-party / competitor data	Restricted to assets you own or manage	Any publicly indexed company or profile content

Use LinkedIn's official API when you already manage approved LinkedIn assets and need first-party analytics or job syndication. Use LinkedIn B2B Emails Scraper: Verified Email Finder when you need to discover public business emails tied to a keyword or industry without going through LinkedIn's partner approval process.

How to use LinkedIn B2B Emails Scraper: Verified Email Finder

LinkedIn B2B Emails Scraper: Verified Email Finder runs on Apify — there's no separate sign-up, API key, or LinkedIn account to configure before starting.

1. Open the Actor's page in Apify Console and click Try for free (or Start, if you already have it saved to your account).
2. Provide at least one value in searchKeywords — the run exits immediately with an error if this array is empty, even though the input schema doesn't mark it as strictly required.
3. Optionally set classificationMode, allowedDomains, geoFilter, and patternSelectors to narrow results to one company, region, or search style.
4. Click Start to launch the run.
5. Open the Output tab to view or export results as JSON, CSV, or Excel — rows appear live as they're found, even before the run finishes.

How to scale to bulk LinkedIn B2B email extraction

searchKeywords accepts an array, so a single run can search dozens of industries, job titles, or company names at once — each keyword is processed against every selected B2B pattern. There's no separate "bulk mode" input: scaling up means adding more keywords (and, in corporate mode, more patternSelectors) to the same array, up to the maxLeads cap of 50,000 per run. For volumes beyond that, or to keep runs isolated per client or campaign, start multiple runs with different keyword sets — Apify's Actor API lets you trigger many runs in parallel.

What can you do with LinkedIn B2B email data?

• A sales development rep building an account-based outreach list sets allowedDomains to a target company's domain and uses the returned email and title fields to populate a cold-email sequence without manually searching LinkedIn.
• A growth marketer running local campaigns combines geoFilter with an industry-specific searchKeywords list, then uses company and domain to group leads by business for city-specific outreach.
• An ABM (account-based marketing) team turns on groupByDomain to get one row per company with a leadCount and nested leads[], ready to drop into a CRM's company/contact hierarchy.
• A recruiter sourcing candidates sets patternSelectors to careers_hiring and hr_recruitment to surface HR and hiring-contact emails instead of general business addresses.
• An AI agent building a lead-enrichment pipeline consumes the typed email, domain, and company fields directly as structured context for an LLM-driven outreach-personalization tool, with no HTML parsing step required.

How does LinkedIn B2B Emails Scraper: Verified Email Finder handle rate limits and blocking?

LinkedIn B2B Emails Scraper: Verified Email Finder handles anti-bot defenses automatically rather than asking you to manage proxies. Each request rotates between four realistic desktop user-agent strings and three Accept-Language headers, and is spaced out with a randomized 1.2–2.8 second delay (2–5 seconds after a block) so requests don't fire in a detectable rhythm. Responses are checked for Google's block signals — a non-200 status, or a small response body containing phrases like "captcha," "unusual traffic," or "before you continue" — and a blocked response triggers automatic proxy escalation: direct connection → Apify's GOOGLE_SERP datacenter proxy → residential proxy, with up to 3 attempts at the residential tier before giving up on that specific query. Setting enableSmartProxy to false disables all escalation and keeps every request direct-only. If a single search query exhausts all escalation attempts, the Actor logs a warning, skips that query, and moves on to the next keyword or pattern rather than stopping the run. If a query returns no new results for 3 consecutive pages, it stops paging for that query. Only an unhandled, unexpected error can stop the whole run — and even then, any leads already collected before the error are still saved.

⬇️ Input

LinkedIn B2B Emails Scraper: Verified Email Finder accepts 11 input parameters, all optional (none are marked required in the input schema, though a run needs at least one search keyword to actually collect anything).

Parameter	Required	Type	Description	Example Value
searchKeywords	No	array	Industries, job titles, or company names to search for on LinkedIn via Google (e.g. marketing, fitness, real estate).	["marketing", "real estate"]
classificationMode	No	string	b2b = only non-Gmail/Yahoo/Outlook business emails; personal = broader discovery of all email types.	"b2b"
allowedDomains	No	array	Restrict returned emails to ONLY these domains (e.g. microsoft.com). Applies to BOTH modes — an email is kept only when it truly ends with one of these domains. Leave empty to disable domain enforcement.	["microsoft.com"]
patternSelectors	No	array	Corporate mode only: empty list runs all patterns; or name specific keys from b2b_patterns.py (e.g. email_for_bookings, bio_email_basic).	["email_for_bookings", "bio_email_basic"]
targetNetwork	No	string	Platform searched for email discovery (locked to LinkedIn.com).	"LinkedIn.com"
geoFilter	No	string	Geographic filter added to search queries (e.g. London, New York). Leave empty for global results.	"London"
maxLeads	No	integer	Maximum number of email leads to collect across all keywords and patterns (1–50000).	500
maxLeadsPerPattern	No	integer	Cap leads collected per B2B search pattern, corporate mode only (1–5000).	50
groupByDomain	No	boolean	When ON, also writes a CRM-style grouped export — one row per resolved company domain with its lead count and full lead list — to a separate per-run dataset. Default: false.	true
enableSmartProxy	No	boolean	Enable proxy for Google Search requests. Recommended: on for best results.	true
proxySettings	No	object	Optional proxy override when Enable Smart Proxy is on. Leave as default for best performance.	{ "useApifyProxy": true, "apifyProxyGroups": ["GOOGLE_SERP"] }

Example input

{
  "searchKeywords": ["marketing", "real estate"],
  "classificationMode": "b2b",
  "allowedDomains": ["microsoft.com"],
  "patternSelectors": ["email_for_bookings", "bio_email_basic", "contact_at_domain", "business_development"],
  "targetNetwork": "LinkedIn.com",
  "geoFilter": "London",
  "maxLeads": 500,
  "maxLeadsPerPattern": 50,
  "groupByDomain": true,
  "enableSmartProxy": true,
  "proxySettings": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["GOOGLE_SERP"]
  }
}

⬆️ Output

Every row is typed, normalized JSON with a consistent schema across runs, exportable as JSON, CSV, Excel, or the other formats Apify's dataset export supports. Each row is billed as one row_result charged event when it's pushed to the dataset.

Example output

{
  "email": "partnerships@brightpeakmarketing.com",
  "domain": "brightpeakmarketing.com",
  "company": "Brightpeakmarketing",
  "keyword": "marketing",
  "pattern": "business_development",
  "leadType": "b2b",
  "title": "Brightpeak Marketing | LinkedIn",
  "url": "https://www.linkedin.com/company/brightpeak-marketing/",
  "description": "Brightpeak Marketing is a full-service growth agency. For partnership inquiries, email us at partnerships@brightpeakmarketing.com.",
  "network": "LinkedIn.com",
  "location": "London",
  "scraped_at": "2026-07-25T14:32:07Z"
}

When groupByDomain is on, a second per-run dataset (named <runId>-companies) is also written, with one row per resolved domain:

{
  "domain": "brightpeakmarketing.com",
  "company": "Brightpeakmarketing",
  "leadCount": 2,
  "leads": [
    { "email": "partnerships@brightpeakmarketing.com", "...": "..." },
    { "email": "hello@brightpeakmarketing.com", "...": "..." }
  ]
}

How does it work?

LinkedIn B2B Emails Scraper: Verified Email Finder never contacts LinkedIn directly. It sends Google search queries — combining your keywords with a site:linkedin.com filter and, in corporate mode, one of 29 B2B search-pattern templates — using browser impersonation (via impit, mimicking a real Chrome or Firefox client) instead of a full headless browser. Every result page is checked for block signals (response size, CAPTCHA/robot-check text); if Google blocks a request, the Actor automatically escalates from a direct connection to Apify's GOOGLE_SERP datacenter proxy, then to a residential proxy, retrying with randomized delays between attempts. Only text already visible in Google's public search results — titles, snippets, and URLs — is parsed and returned; nothing requires a LinkedIn session. The output schema (the same set of fields on every row) stays stable regardless of how LinkedIn's or Google's page layouts change, since parsing targets Google's result structure, not LinkedIn's.

Integrations

LinkedIn B2B Emails Scraper: Verified Email Finder runs on the Apify platform, so it works with anything that can call the Apify API, plus Apify's own no-code and agent integrations.

Calling LinkedIn B2B Emails Scraper: Verified Email Finder programmatically

from apify_client import ApifyClient

client = ApifyClient("<APIFY_API_TOKEN>")
run = client.actor("scraper-engine/linkedin-b2b-emails-scraper-verified-email-finder").call(
    run_input={
        "searchKeywords": ["marketing"],
        "classificationMode": "b2b",
        "maxLeads": 100,
    }
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Works in Go, Ruby, Node.js, cURL — any language that can make an HTTP request.

MCP integration for AI agents

This Actor is reachable through Apify's official MCP server, so an AI agent can call it as a tool instead of custom integration code. In Claude Desktop or Claude Code, add a connector pointed at https://mcp.apify.com and authorize your Apify account, or run the server locally with npx @apify/actors-mcp-server --actors scraper-engine/linkedin-b2b-emails-scraper-verified-email-finder (APIFY_TOKEN set in the environment). Any MCP-aware client can then call this Actor directly.

No-code tools (n8n, Make, LangChain)

In n8n, use the Apify node (or an HTTP Request node against the Apify run-sync-get-dataset-items endpoint) to trigger a run and pull results into your workflow. In Make, the Apify app's "Run an Actor and get dataset items" module does the same. In LangChain, Apify's integration lets you call this Actor as a tool or load its dataset directly into a document loader for a lead-enrichment RAG pipeline.

Is it legal to scrape LinkedIn B2B emails?

Scraping publicly available data is generally permitted in most jurisdictions, and LinkedIn B2B Emails Scraper: Verified Email Finder only returns data that is already publicly indexed by Google — no login, password, or session cookie is ever used to access LinkedIn. Because the output is email addresses tied to real people and companies, it counts as personal data under GDPR and CCPA even when the email is business-branded (e.g. jane@company.com) — the same rules that apply to any personal-data collection apply here: you need a lawful basis (e.g. legitimate interest for B2B outreach), you must honor deletion/opt-out requests, and you should not use collected addresses for spam or bulk unsolicited messaging. This Actor does not verify mailbox deliverability, so treat every result as a discovered public mention, not a guaranteed-valid inbox. Consult legal counsel if your use case involves bulk storage or processing of personal data.

Frequently asked questions

What LinkedIn B2B email fields does LinkedIn B2B Emails Scraper: Verified Email Finder return?

It returns email, domain, company, leadType, and keyword as the core fields, plus pattern, url, title, description, network, location, and scraped_at. See the full fields table above for every key.

Does LinkedIn B2B Emails Scraper: Verified Email Finder require a LinkedIn account or login?

No. It searches Google for public LinkedIn content and never authenticates against LinkedIn — no cookies, credentials, or session tokens are used.

How many leads can I extract in one run?

Up to maxLeads, capped at 50,000 per run. How many you actually get depends on how many matching public results exist for your keywords and patterns — the Actor stops paging a query after 3 consecutive pages return no new results.

What happens if a search keyword returns no email matches?

That keyword (or, in corporate mode, that keyword/pattern combination) simply produces zero rows — the Actor stops paging it after 3 consecutive empty pages and moves on to the next keyword or pattern rather than failing the run. Other keywords in the same run keep collecting normally.

Can I scrape multiple LinkedIn keywords at once?

Yes. searchKeywords accepts an array, and in corporate mode each keyword is run against every selected entry in patternSelectors — no need for separate runs per keyword.

Does LinkedIn B2B Emails Scraper: Verified Email Finder work with Claude, ChatGPT, and other AI agent tools?

Yes. It's reachable through Apify's MCP server for Claude and other MCP clients, and callable as a standard HTTP API endpoint by any agent framework that can make a request.

What does "verified" actually mean for these emails?

It does not mean the mailbox has been SMTP-checked or run through a third-party deliverability API — the source code contains no such check. "Verified" refers to the email being confirmed present in a live, public Google search result at the time of the run, then classified as corporate or personal and, if you set one, matched against your domain allowlist. Treat results as discovered public mentions, not guaranteed-deliverable addresses.

Does LinkedIn B2B Emails Scraper: Verified Email Finder return data in a format LLMs can use directly?

Yes. Output is typed, normalized JSON with consistent field names across runs — no HTML parsing or CSS selectors required. Pass it directly to an LLM, index it into a vector store, or feed it to an agent tool.

What happens when LinkedIn or Google changes its layout or anti-bot system?

The Actor is maintained and its output schema stays stable across such changes, since it parses Google's result structure rather than LinkedIn's page markup. No specific update turnaround time is published or guaranteed.

Can I use LinkedIn B2B Emails Scraper: Verified Email Finder without managing proxies or browser infrastructure?

Yes. The Actor handles user-agent rotation, request timing, and 3-tier proxy escalation (direct → Apify datacenter → residential) automatically; you only need to supply your own proxySettings if you want to override the default Apify proxy behavior.

Which fields work best for AI training data and RAG indexing?

For RAG, index description and title — the free-text fields with the most contextual detail. For training data or feature pipelines, leadType, domain, company, and network are the most consistently structured fields across every row, all returned as typed primitives (strings).

Related scrapers

Scraper	What it extracts
LinkedIn Company Scraper & Open Jobs Finder	Firmographics and open jobs
LinkedIn Company About Scraper	Company "About" page details
LinkedIn Company Employees : AI & Lead Enrichment Scraper	Employees with AI sentiment scoring
LinkedIn Post Scraper	Post content and engagement
LinkedIn Profile & Credibility Analysis Scraper	Profile data plus credibility analysis
extract-emails-contacts-socials-from-any-website	Email/contact discovery via Google search, any platform

Your feedback

Found a bug or a field that doesn't match your data? Let the Scraper-Engine team know through the Issues tab on this Actor's Apify Store page, or via the developer contact listed there. Reports like these are what keep the search patterns and classification logic current as LinkedIn and Google change.