Free prospecting workspace

Bring the results back.
Keep the originals.

Join external enrichment results to your LinkedIn audience by explicit profile URL keys. Keep supplied fields separate, hold ambiguous groups and download the evidence for review.

Local file processing. No signup required.

Join an audience with supplied results

Matched keys, unmatched audience, orphan results and review originals stay separate. This tool finds no emails and verifies no provider status.

Original audience

Keep your source observations

No file loaded

External results

Keep the supplied evidence

No file loaded

Load two CSVs, or use the fictional exercise. Select both identity columns before joining.

Finish the job with the original exercise

Read the enrichment reconciliation guide for the worked case, native Clay/n8n alternatives and how to build a reviewed destination payload. All example names, profile URLs, emails and statuses are fictional. The labels synthetic=TRUE and do_not_contact=TRUE do not enforce a destination blocklist.

What each output means

Matched key pairs: exactly one usable key record on each side, with both files' fields preserved. The label matched_key_only does not establish identity, email deliverability, employment or contact permission.

Unmatched audience: original rows without a corresponding enrichment key. Orphan enrichment: supplied rows outside the original key set. Neither is silently appended to the matched audience.

Review originals: duplicate keys, conflicting duplicate records, invalid identities and width-mismatched CSV rows are held with original cells and provenance. A malformed-width record with a usable key also holds its otherwise matching partner.

Keys normalize a conservative public-person URL shape while preserving slug case and encoding. Names, email values and row order never create a match. A changed URL alias can therefore appear unmatched or orphaned until you resolve it manually.

This browser tool accepts files up to 5 MiB each. This local file-size setting was checked 12 October 2026. It is this tool's input file-size limit, not a LinkedIn or enrichment-provider quota. Excel-safe CSV output prefixes formula-like cells with an apostrophe. Turn it off only when you need the original supplied text for a reviewed import; the original parsed-record JSON remains unmodified.

Frequently asked questions

Does this tool find or verify email addresses?

No. It joins supplied CSV records by the selected public profile URL key. Email addresses, statuses and evidence stay exactly as supplied. A matching key or a provider label is not verification by this tool.

Are my CSV contents sent to a server?

The tool reads and joins the files locally in your browser and makes no external profile or enrichment requests. Clear workspace removes the loaded data from this page. Your original files, downloaded copies and destination records remain.

What happens when more than one row has the same profile key?

All records in that key group from both files go to review, including identical duplicates. They do not appear in matched, unmatched or orphan outputs. Conflicting duplicate values are retained; the tool does not select the latest record.

Why are source and enrichment fields separate?

They are separate observations. The output labels every input column by its side and position, preserving duplicate headers and supplied values. Choose a reviewed destination payload after the join; the tool never silently overwrites the source company, title, email or status.

Can I match names, Sales Navigator IDs or changed profile aliases?

No. Choose a public-person LinkedIn URL column explicitly in each file. Blank, company and unresolved Sales Navigator values go to review. Slug case and encoding are preserved; the tool makes no name fallback or external alias resolution.

The next source audience

Source the people your next job needs.

When your existing approved audience is insufficient, test the published 100-profile signup allowance without a card. Offer checked 12 October 2026: current source offers. Inspect the real export and current terms before choosing more source volume. This joiner stays free.

Test my first profile audience
Keep a working native workflow.

If your enrichment already stays attached to the original Clay table or n8n items, use that route. Additional CSV transfer is useful when you need to reconcile two existing files.

Native lookup and matching alternatives
Current extraction offers