API docsAgent tools

Chrome extension

Find contacts on LinkedIn with the Chrome extension

In short

How do I find someone's email address on LinkedIn using the Reply extension?

Browse LinkedIn, Sales Navigator or Recruiter with the extension open, and it lists the people on the page; click Reveal details for one person, or tick several and reveal them together. Reply works out the likely addresses from the name and company domain and verifies them through your own Google session, labeling each result Valid, Risky, Catch all or Invalid. Finds are capped at 300 email searches per hour for each user, and only searches that actually return an address count towards it.

Goal

A screen of LinkedIn profiles turned into named people with checked addresses, ready to save: the browser half of prospect search and data enrichment.

Preconditions

A signed-in extension (see Install the Reply Chrome extension) and a Gmail session loaded in the same browser profile, since address verification runs through it. Revealing spends Data Search credits and requires the data-search permission on your user, so check both before a long run: the extension shows your credits used against the total your plan grants.

Steps

  1. Open one of the three LinkedIn surfaces the extension reads. Public LinkedIn people search is one; Sales Navigator search results and saved lead lists are the second; LinkedIn Recruiter and Talent searches are the third. Each has its own individual and bulk path, and all of them feed the same Search tab in the extension.
  2. For one person, open their profile. The extension pulls their public details (first and last name, title, company and domain, industry and company size, city, state and country, plus the profile links) and fills its own card with them.
  3. For a screen of people, run the search on LinkedIn first, then scroll so the results you want are actually rendered. The extension collects whatever the current page is showing; there is no fixed batch size, so what you scroll is what you get. On Recruiter, start the bulk search and click Find emails to make the extension populate names and begin looking.
  4. Click Reveal details for a single card, or tick the cards you want (or the select-all control above them) and reveal the selection in one action. The button reads Revealing while the run is in flight.
  5. Watch the quality label that lands next to each address: Valid email, Risky email, Catch all ("External server accepts fake and nonexistent addresses, so this email may not exist") or Invalid email. Treat Catch all as unconfirmed rather than wrong: the receiving server accepts anything, so nothing was proven either way.
  6. Adjust how hard the search tries in the extension's Settings: Advanced search mode widens the set of address patterns Reply tests for each person, and Search for personal emails decides whether personal addresses are looked for alongside work ones. Save contacts without email lets a person be stored even when nothing is found, with a stand-in address marked "Generated email to save contact in Reply".
  7. Hovering works too, without a search: pass the cursor over a person on LinkedIn and the extension opens a create-contact screen with first name, last name, title, company, city, country and the profile link already filled in, or the edit screen if you already have them. Whether that hover behavior is active for you is a setting: open Settings and check before relying on it.

Expected result

Revealed cards carry an address with a quality label, and the company details sit alongside the person. A card that came back without an address is not a failure of billing; nothing is charged for a search that finds nothing.

Verification

Compare the credit counter in the extension before and after a run. It should drop by one for each person who was genuinely new to your account: an address you already hold reuses the existing record and costs nothing, which is why a bulk reveal over a familiar list can leave the counter almost untouched.

What happens next

Revealed people are still only in the extension until you push them across. See Save contacts from the extension into Reply. Once they are in, the usual deduplication rules apply to them like any other contact.

Common mistakes

  • Reading "Prospect not revealed due to hourly search limit exceeding. Try again within an hour." as an outage. It is the per-user ceiling of 300 successful email searches an hour. The hour starts at your first successful find and the whole allowance returns at once, and your teammates have their own; nobody drains yours.
  • Assuming a bulk run that hit the ceiling only lost one person. Messages are throttled, so one notice can stand for a whole batch; the bulk wording counts them for you.
  • Closing every Gmail tab. Without that session the search cannot start and you get "Email search initialisation failed. Please open gmail in new browser tab or click here to fix.": the link in that message restarts the Google side, which is usually all it needs.
  • Revealing a profile with no company domain to work from, or with both name fields empty. There is nothing to build candidate addresses out of, so the search stops before it begins.
  • Confusing an empty allowance with a blocked feature: "Prospect not revealed due to prospect limit exceeding. Please contact support." means the Data Search side, not LinkedIn.

Build with Reply

  • REST API: docs.reply.io – search and enrichment endpoints for the same data
  • Agent skills: agents.reply.io/skills – the audience-building skill covers list creation end to end