Find work emails and phone numbers

Contact discovery enriches a known person. Company and people search do not return these contact details automatically.

Enable discovery for the workspace

A workspace owner or admin opens Settings → Contact data, enables Professional emails and/or Direct phone numbers, confirms lawful business use, chooses an email and phone profile, sets Maximum agent batch credits, and saves.

Profiles are Fast, Balanced and Highest coverage. Leadbase owns provider routing; you do not supply provider credentials or select an upstream endpoint. Enabled settings do not guarantee that a route is currently available or that sufficient credits remain.

Identify the person

• Work email: use a canonical LinkedIn profile, or a first name, last name and company domain.
• Phone: use a canonical LinkedIn profile. A name and company alone are insufficient.
• Add corroborating company, title, name and two-letter country information when known. Use a lowercase company hostname without a scheme or path. A canonical LinkedIn URL has the form https://www.linkedin.com/in/profile-slug, without a query, fragment or trailing slash.

Ask the assistant to find the contact data for the identified person and write a found result to the intended email or phone column. Inspect identity and result before outreach.

Results and credits

These are the current contact-tool states; they do not include a public pending result. Operational research and billing can still be queued or unresolved separately. A new request delivering a cached contact is charged too. Exact replay of the same request does not charge again. Other AI or research usage is separate; see Credits.

Quality is verified, likely or unknown. Phone output also includes an E.164 number, a mobile, direct, work or unknown type, and an extension when returned. Quality does not establish current employment, consent or permission to contact the person.

API and MCP callers

prospects.find_email and prospects.find_phone are version-2 operations. Each call accepts one identity, plus an idempotencyKey. There is no people array or 50-person contact batch in the current input contract. MCP names are prospects_find_email and prospects_find_phone.

Work email input

This illustrative identity uses reserved example data. Replace it with a reviewed real identity; explicitly send null for unknown fields required by the schema.

{  "idempotencyKey": "email-jane-example-001",  "identity": {    "kind": "person_at_company",    "firstName": "Jane",    "lastName": "Example",    "companyDomain": "example.org",    "companyName": null,    "countryCode": null,    "jobTitle": null  }}

Phone input

{  "idempotencyKey": "phone-jane-example-001",  "identity": {    "kind": "linkedin",    "linkedinUrl": "https://www.linkedin.com/in/jane-example",    "firstName": null,    "lastName": null,    "companyDomain": null,    "companyName": null,    "countryCode": null,    "jobTitle": null  }}

Keep the returned requestId, result and key for each person. A new identity or lookup needs a new key. After a lost response, recover the same request with identical input; do not turn an uncertain outcome into a new paid submission. Respect the workspace budget and admission rules when iterating over Sheet rows.

A failed result contains a code such as temporarily_unavailable, result_unavailable or unavailable. A transport failure can instead be a permission, credit or conflict error. Neither means the person has no contact data. See API errors and recovery.