Sourcing
Capture extensions are how most databases fill up with the same person four times.
One click, one new record, no check. Eighteen months later nobody trusts a search result, and the fix is a de-duplication project nobody wants to run.
The decision that makes it safe
It asks whether you already have them, before it writes.
Select the people you want and the extension checks each one against your database first. You are told, per row, whether saving will link to somebody you already have or create a new person — and only then do you press save.
That check is the difference between a sourcing tool and a slow-motion data quality problem.
- Person AData engineering leadAlready yourslinks to someone you met in 2024
- Person BSenior data engineerNewcreates a new person
- Person CAnalytics managerAlready yoursalready a contact at a client
- Person DPlatform engineerNewcreates a new person
- Bulk, with per-row control —
From a search results page, save the visible rows in one action — but as rows you selected, having seen which are already yours.
- Sales Navigator too —
Lead and people records, company records, and Navigator search lists. Where a Navigator card points back at the public profile, that is used as the identity key — which is the detail that keeps Navigator captures and ordinary ones from becoming two different people.
- Candidate, contact or account —
The same person can be a candidate on your side and a contact at a client. A company page saves as an account, and saving it twice does not make two.
- Credentials are never touched —
It reads the page you are already looking at. There is no login to LinkedIn stored, transmitted or requested — which is both a security answer and a terms-of-service one.
What happens to a captured person
They land as a record, not as an application.
Capture creates or links the person, and can attach them to a client account. It does not put them onto a requisition — that is a deliberate second step you take in the product, because sourcing somebody and submitting them are different decisions and conflating them is how people get sent to clients by accident.
Once they are in, everything else applies: the CV reads with its source lines, the free pass scores them against your open roles, and your custom fields fill themselves.
The practical questions
Mostly about safety and scope.
›Does it need our LinkedIn login?
No. It reads the page open in your own browser. No credentials are stored, sent or asked for.
›Does it put people straight onto a role?
No — it creates or links the person, and optionally attaches them to a client account. Putting them on a requisition is a separate step by design.
›Will it create duplicates?
It tells you before it writes. A row that matches somebody you have links to them instead of creating a second copy.
›Does it work with Sales Navigator?
Yes — lead, people, company and search-list surfaces.
›Is this a differentiator?
Capture is not. Most vendors ship one. The probe before the write is unusual, and that is the only part of this page we would argue about.
Book a demo
Capture four people from one search.
Include somebody you are fairly sure you already have. What the popup says about that row is the whole point.