LinkedIn Profile Finder: LinkedIn URLs from an email or a name and company

Find the LinkedIn profile behind a contact. Give it email addresses, or names with a company domain, or a mix of both, and get back the best-matching LinkedIn profile URL for each. Use it to attach LinkedIn profiles to CRM records, check you have the right person before outreach, or prepare a list for LinkedIn enrichment. Powered by MoltSets.

• From an email: business or personal addresses. MoltSets scores every candidate profile and returns the single best match.
• From a name and company: Jane Doe, acme.com. When several people match, the best match comes first and the others are listed, so you can pick the right one.
• Mixed lists: emails and names can sit in the same list or dataset. Rows with an email are looked up by email; the rest by name and company.
• Works with any lead list: map your dataset's email, name and company columns, or let the Actor detect common column names.
• Clean input: duplicates, missing names and company names given instead of domains are flagged without spending anything.

Bring your own MoltSets API key

This Actor calls the MoltSets API with your own key, so MoltSets data is billed to your MoltSets account and Apify only charges for compute (the Actor itself is free).

1. Create a free MoltSets account.
2. Copy a key from API keys. Keys start with ms_.
3. Paste it into the MoltSets API key field. Apify stores it encrypted and the Actor never logs it.

What it costs

You only pay for hits. A lookup that finds nothing costs no tokens. It still counts towards your MoltSets Fair Use request limits.

Lookup	MoltSets tool	Cost
Email to LinkedIn	email_to_linkedin	1 token per profile found
Name and company to LinkedIn	search_linkedin_profile	1 token per search with a match

Costs are read live from your account (get_billing) at the start of every run, and the log shows a worst-case estimate before any lookups are made. If your balance is lower than the worst case the run still starts, because misses are free; if tokens run out it stops gracefully and keeps everything found so far.

Token costs are the published MoltSets rates at the time of writing. Lookups that find nothing cost nothing. To go further, the LinkedIn Profile Enricher turns the URLs into full profiles, and the Reverse Email Lookup returns the person and company behind an email in one step.

Input

Field	Name	Default	Description
apiKey	MoltSets API key		Required. Your MoltSets API key (starts with ms_). No account yet? Sign up free, then copy a key from API keys. MoltSets bills your MoltSets account directly, and only for hits.
lookups	Emails or names		One per line: an email address (jane@acme.com), or a name and company domain (Jane Doe, acme.com). Business and personal emails both work. Duplicates are removed before any lookup.
datasetId	Read from a dataset		Use the results of another run, for example a lead list or CRM export. Rows with an email are looked up by email; rows without one by name and company. Combined with any lines above.
emailField	Email column		Leave empty to try email, Email, emailAddress, email_address, workEmail, businessEmail and contactEmail.
nameField	Full name column		Used for rows without an email. Leave empty to try fullName, full_name, name and Name. Not needed when first and last name columns are set.
firstNameField	First name column		Leave empty to try firstName, first_name and First Name.
lastNameField	Last name column		Leave empty to try lastName, last_name and Last Name.
companyField	Company domain column		Column with the company domain or website. Leave empty to try companyDomain, company_domain, companyWebsite, company_website, website, domain, companyUrl, Website and Domain. Dot paths work.
maxItems	Maximum lookups	100	Hard cap on unique lookups processed in this run.
maxRetryWaitSecs	Longest Fair Use wait	120	If MoltSets asks the run to wait for a Fair Use window up to this long, it waits and carries on. Longer waits stop the run gracefully and keep the results so far.

Example input:

{
    "apiKey": "ms_XXXXXXXXXXX",
    "lookups": [
        "jane.doe@acme.com",
        "John Smith, example.com"
    ],
    "maxItems": 100
}

Output

One row per input item, in input order. Each lookup has a <lookup>_status column:

Status	Meaning
found	Data returned (and charged).
not_found	Nothing on file. Free.
restricted	Not included in your MoltSets plan. Nothing charged. See notes.
skipped	Not attempted: invalid input, out of phone tokens, or the run stopped early. See notes.
error	MoltSets could not complete the lookup after retries. Free; worth running again.

Example row:

{
    "input": "John Smith, example.com",
    "input_type": "person",
    "input_email": null,
    "input_name": "John Smith",
    "input_company": "example.com",
    "input_status": "valid",
    "linkedin_status": "found",
    "linkedin_url": "https://linkedin.com/in/john-smith-123",
    "matched_name": "John Smith",
    "match_count": 2,
    "linkedin_other_matches": "https://linkedin.com/in/john-smith-456",
    "linkedin_source": "search_linkedin_profile",
    "notes": "2 profiles match this name at this company; check linkedin_other_matches."
}

• Check common names. When match_count is above 1, linkedin_url is MoltSets' best match and the rest are in linkedin_other_matches.
• Email lookups return one profile, so match_count is 1 when found.

A run summary (hits and misses per lookup, tokens used, skipped lookups and why, stop reason) is saved as SUMMARY in the run's key-value store and shown in the run's status message.

Chaining from a scraper

Point the Actor at any dataset with emails, or with names and company websites. In the Console, choose it under Read from a dataset; common column names such as email, fullName, firstName, lastName and website are detected automatically.

From code, with the Apify API client:

import { ApifyClient } from 'apify-client';

const apify = new ApifyClient({ token: process.env.APIFY_TOKEN });

const run = await apify.actor('moltsets/linkedin-profile-finder').call({
    apiKey: process.env.MOLTSETS_API_KEY,
    datasetId: '<dataset with an email column>',
    maxItems: 500,
});

const { items } = await apify.dataset(run.defaultDatasetId).listItems();

To run it automatically after another Actor, add an integration on that Actor that starts this one with {"datasetId": "{{resource.defaultDatasetId}}"} plus your key.

Limits

• Company domain needed for names: a company name such as Acme Inc is not enough. Use the website domain.
• Fair Use: email lookups fall under the Fair Use Policy for Enrichment and name searches under the Fair Use Policy for Search. Every lookup counts as a request, hit or miss. If MoltSets asks the run to wait less than Longest Fair Use wait (default 120 seconds) it waits and continues; otherwise it stops gracefully and keeps its results.
• Speed: name searches run three at a time to stay inside MoltSets' search concurrency limits on every plan.
• Out of tokens: the run stops, keeps everything processed so far and links to billing. Unprocessed rows are marked skipped.
• Maximum lookups caps unique lookups per run (default 100), so a large dataset cannot spend more than you intended.

Other MoltSets Actors

• LinkedIn Email and Phone Finder (coming soon): business and personal emails, mobile phones and hashes from LinkedIn URLs.
• Email Finder by Name and Company (coming soon): business emails from a name and company domain.
• Reverse Email Lookup (coming soon): the person and LinkedIn profile behind an email address.
• IP to Company Lookup (coming soon): the company behind an IPv4 address.
• LinkedIn Profile Enricher (coming soon): full profile, emails and company firmographics from LinkedIn URLs.
• B2B Lead List Builder (coming soon): lead lists of people or companies by title, industry, location and size.
• Audience Match Keys (coming soon): hashed emails and mobile ad IDs for customer match audiences.

Support

• MoltSets API docs: developer.moltsets.com
• Account, billing and plan questions: support@moltsets.com
• Bugs in this Actor: open an issue on the Issues tab.