How to find emails from LinkedIn profiles

Why LinkedIn is the best source for B2B emails

LinkedIn is the world's largest professional network, with over 900 million members across every industry and role. For sales, recruiting, and marketing teams, it is the richest source of B2B contact data on the internet. LinkedIn intentionally hides email addresses on profiles, so to move conversations off-platform you need a separate way to resolve a name and a company into a verified work email.

Mailsfinder solves this by taking the public signals you already have (a person's full name and their company's domain) and returning a verified business email in real time. You can do this one profile at a time through the dashboard, in bulk through a CSV upload, or programmatically through the REST API.

The workflow at a glance

1. Identify your target profiles on LinkedIn (regular search, Sales Navigator, or a saved list).
2. Capture each person's full name and company domain.
3. Either upload a CSV to the Mailsfinder bulk finder, or call the Mailsfinder REST API with name and domain.
4. Mailsfinder resolves the email pattern and verifies the result via SMTP in real time.
5. Download the enriched CSV, or push results into your CRM or sequencer through n8n, Make, or Zapier.

Step 1: Identify your target profiles on LinkedIn

Start by building the list of people you actually want to contact. There are three common ways to do this:

• Regular LinkedIn search. Good for ad-hoc lookups of 1 to 20 people. Use job title, company, and location filters to narrow down.
• Sales Navigator search. The right choice for serious prospecting. You get advanced filters like headcount, seniority, function, technology used, and recent job changes.
• Saved lead lists. If you already maintain lists inside Sales Navigator, you can pull them straight into a CSV later in this workflow.

Step 2: Capture name and company domain

Mailsfinder needs two inputs to find a verified email: the person's full name, and the company domain (not the company name). For example, "Jane Doe" and acme.com, not "Jane Doe" and "Acme Corp."

For a handful of profiles, copy the name and look up the company website manually. For anything larger, export from Sales Navigator. A clean CSV with two columns (name, domain) is all you need.

If you only have a LinkedIn URL or a company name, do a quick lookup of the company website first (the domain is almost always linked from the LinkedIn company page). Mailsfinder cannot resolve an email from a LinkedIn URL alone, so the domain step is required.

Step 3a: Upload a CSV to the bulk finder

For most users, the bulk CSV finder is the simplest path. Inside your Mailsfinder dashboard:

1. Go to Bulk Finder and click Upload CSV.
2. Map your columns to first_name, last_name, and domain. Mailsfinder auto-detects most headers.
3. Confirm and start the job. The finder runs the lookup and SMTP verification on every row.
4. When the job completes, download the enriched CSV. Each row gets an email, a status (valid, risky, invalid, not found), and a confidence score.

A 1,000 row file typically completes in a few minutes. Each successful find consumes one credit.

Step 3b: Call the REST API directly

If you want to automate the workflow or integrate it into your own product, use the Mailsfinder REST API. The core endpoint is POST /v1/find, which accepts a name and a domain and returns a verified email.

POST https://api.mailsfinder.com/v1/find
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "first_name": "Jane",
  "last_name": "Doe",
  "domain": "acme.com"
}

A typical response:

{
  "email": "jane.doe@acme.com",
  "status": "valid",
  "confidence": 96,
  "smtp_check": "passed",
  "pattern": "{first}.{last}@{domain}"
}

The status field can be valid, risky (catch-all domain), invalid, or not_found. Use valid for outreach with confidence. Treat risky results with care: they will land, but you cannot confirm the mailbox exists without sending.

Step 4: How the verification works

Behind both the bulk finder and the API, Mailsfinder runs the same pipeline. It identifies the company's email pattern from public signals, generates the candidate address, and then opens an SMTP conversation with the receiving mail server to check whether the mailbox accepts mail. The full lookup typically takes 2 to 6 seconds per contact.

Real-time SMTP verification is what keeps bounce rates low. You do not need to run a separate verification step before sending.

Step 5: Push results into your CRM or sequencer

Most users do not stop at a downloaded CSV. To get LinkedIn-sourced emails into your outbound stack automatically, connect Mailsfinder to your CRM or sequencer through a workflow tool:

• n8n. Build a workflow that watches a Google Sheet or webhook, calls POST /v1/find, and writes results to HubSpot, Salesforce, Smartlead, Instantly, or Apollo.
• Make (formerly Integromat). Use the HTTP module to call the Mailsfinder API and route results through any of Make's 1,500+ app modules.
• Zapier. Same pattern using Zapier's Webhooks action. Good if your team already lives in Zapier.

A common setup: Sales Navigator export goes into a Google Sheet, n8n picks up new rows, calls Mailsfinder, and pushes valid emails straight into a sequencer. You never touch the CSV manually after the first export.

LinkedIn-specific gotchas

Sales Navigator export limits

Sales Navigator caps list exports at 2,500 leads per saved list. For larger searches, split your filters by geography, headcount band, or seniority to keep each list under the cap. You can then run each CSV through the bulk finder separately and merge the results.

Profiles without a confirmed work email

Not every profile resolves cleanly. Common reasons: the person uses a personal address as their work email, they recently moved companies and their old domain is stale, or their employer runs a strict catch-all setup. When Mailsfinder returns not_found or risky, consider reaching out on LinkedIn instead or skip that row.

LinkedIn URL-only inputs

If your starting point is a LinkedIn URL with no parsed name or domain, do a one-time enrichment step first (a quick scrape of the public profile gives you the name; the company page gives you the domain). Mailsfinder needs both before it can run.

GDPR and EU profiles

If you are emailing EU residents for B2B outreach, you must have a lawful basis under GDPR (typically legitimate interest), keep your outreach relevant to the recipient's professional role, honour every opt-out, and offer a clear unsubscribe path. Mailsfinder returns business email addresses only, which sit inside the B2B exemption in most EU markets, but the legal responsibility for outreach rests with you.

Best practices for LinkedIn email finding

• Capture the domain, not the company name. "acme.com" works. "Acme Corp" does not.
• Send only to valid results. Treat risky and not_found rows as a separate, lower-priority segment.
• Personalise with LinkedIn context. Reference a recent post, a shared connection, or a role change in the first line. The data that made you find the email is also what makes the email worth replying to.
• Respect opt-outs across channels. If someone asks not to be contacted, suppress them everywhere, not just in the tool that received the reply.
• Batch your runs. A few large weekly jobs is cleaner than thousands of small lookups scattered through the day.

Pricing context

Every Mailsfinder plan includes 100 free credits per day, forever, which covers casual LinkedIn lookups at no cost. For higher-volume LinkedIn prospecting, the $9.99 per month plan gives you 300,000 credits, and the $249 lifetime plan gives you 2 million credits with no recurring fee.

Summary

You do not need a browser add-on to turn LinkedIn into a pipeline of verified emails. Identify your targets on LinkedIn, capture name and domain (manually for small lists, Sales Navigator export for larger ones), push the list through the Mailsfinder bulk finder or the REST API, and wire the results into your CRM or sequencer through n8n, Make, or Zapier. The whole loop is faster, more reliable, and far easier to scale than profile-by-profile lookups.