Apollo Email Lookup for One Person

Use a known email, public LinkedIn profile, or name with a company website to find one person. Review the professional details Apollo returns; personal email and phone requests stay off by default.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use the existing Toolmu connection and read https://toolmu.com/SKILL.md for setup. Use enrich-a-person-s-details-with-apollo-apollo. Collect at least one clear, user-provided clue: a known email, a public LinkedIn profile URL, a full name plus company website, or a full name plus company name. If none is available, ask the user for one; never ask them to find or provide an Apollo person number. Map only the provided clue to the matching supported Tool input: email, linkedin_url, name with domain, or name with organization_name. If the user directly supplies an Apollo person ID, it may be passed through unchanged, but never request or display one. Make at most one request, only within the user’s authorization and the currently displayed execution terms. Keep reveal_personal_emails and reveal_phone_number false unless the user explicitly requests that specific extra contact lookup and the displayed authorization and price permit it; if not clearly covered, leave them off. Do not call another Tool or retry. Report only the details Apollo actually returns. Keep the company as matching context because it may be a past employer. Treat Apollo’s match assessment as a source clue, not proof of identity or current employment. Keep missing details unknown, do not expose internal IDs, and stop after this one request.

Task:
Look up one person in Apollo using [known email], [public LinkedIn profile link], or [full name] with [company website link]. Review the professional details Apollo returns. Personal email and phone requests stay off. A name alone may not be enough to find a match.

Paste into your connected AI's conversation.

Connection guide

Up to 0.6 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

Apollo

Apollo Email Lookup for One Person

Use a known email, public LinkedIn profile, or name with a company website to find one person. Review the professional details Apollo returns; personal email and phone requests stay off by default.

You receive

The matched record may contain a name, role and headline, employer, location, work history and profile references, plus an available work email, its source status and Apollo’s match-confidence assessment. Your Agent can compare the returned details with the person you intended to match.

Start with your task

Look up one person in Apollo using [known email], [public LinkedIn profile link], or [full name] with [company website link]. Review the professional details Apollo returns. Personal email and phone requests stay off. A name alone may not be enough to find a match.

What to know

Details may be missing or outdated, and a match-confidence assessment does not independently verify identity, current employment or email delivery. Optional personal-email and phone requests do not guarantee contact details; phone results can be delayed, with no guaranteed arrival or completion time. Missing data, no match or retrieval failure does not prove that the person does not exist.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Known-person matching settings`queryParams`	`object`	Optional	Person-identifying information for matching one known person, such as an existing Apollo person ID, known email or LinkedIn profile, or a name with employer context. More relevant information can improve matching. Personal-email and phone request flags do not identify the person.
Apollo person ID`queryParams.id`	`string`	Optional	Optional nonempty string containing an existing Apollo person ID. Use an ID you already have; it is not an organization ID. This example uses only the actual person ID supplied by the user. Minimum length `1`
Full name`queryParams.name`	`string`	Optional	Optional nonempty full-name string, typically first name and surname separated by a space. It can be used instead of separate first-name and surname fields. Employer context can help distinguish names but does not prove a unique identity. Minimum length `1`
Known email address`queryParams.email`	`string`	Optional	Optional nonempty email-address string you already know, used to match a professional record. It does not grant mailbox access or independently verify address ownership or deliverability. Minimum length `1`
Current or past employer domain`queryParams.domain`	`string`	Optional	Optional nonempty employer-domain string without www. or @. It may describe a current or past employer and helps match the person; it does not establish current employment at that domain. Minimum length `1`
Surname`queryParams.last_name`	`string`	Optional	Optional nonempty surname string, usually used with the first-name field. Do not reconstruct a surname from a masked record. Minimum length `1`
First name`queryParams.first_name`	`string`	Optional	Optional nonempty first-name string, usually used with the surname field to identify the known person. Minimum length `1`
Known email hash`queryParams.hashed_email`	`string`	Optional	Optional nonempty string containing an MD5 or SHA-256 hash of the known person’s email. It is a matching input, not a request to recover the email address or access a mailbox. Minimum length `1`
Personal LinkedIn profile URL`queryParams.linkedin_url`	`string`	Optional	Optional nonempty URL string for the known person’s LinkedIn profile. It is a person-matching reference, not a company-page URL or an instruction to browse the profile. Minimum length `1`
Current or past employer name`queryParams.organization_name`	`string`	Optional	Optional nonempty employer-name string that can describe current or previous employment. Use it as context for the known person; it does not establish their present employer or uniquely identify them by itself. Minimum length `1`
Request available phone numbers`queryParams.reveal_phone_number`	`boolean`	Optional	Optional boolean requesting available phone data. Phone processing can be asynchronous, and returned numbers, arrival and completion time are not guaranteed. A pending request is not a completed phone result. The example explicitly sets false.
Request available personal emails`queryParams.reveal_personal_emails`	`boolean`	Optional	Optional boolean requesting available personal emails. Results depend on Apollo’s coverage and regional restrictions; an address is not guaranteed. The example explicitly sets false.

View raw JSON

{
  "type": "object",
  "required": [],
  "properties": {
    "queryParams": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "~standard": {
        "vendor": "zod",
        "version": 1,
        "jsonSchema": {}
      },
      "properties": {
        "id": {
          "type": "string",
          "minLength": 1,
          "description": "Optional nonempty string containing an existing Apollo person ID. Use an ID you already have; it is not an organization ID. This example uses only the actual person ID supplied by the user."
        },
        "name": {
          "type": "string",
          "minLength": 1,
          "description": "Optional nonempty full-name string, typically first name and surname separated by a space. It can be used instead of separate first-name and surname fields. Employer context can help distinguish names but does not prove a unique identity."
        },
        "email": {
          "type": "string",
          "minLength": 1
        },
        "domain": {
          "type": "string",
          "minLength": 1,
          "description": "Optional nonempty employer-domain string without www. or @. It may describe a current or past employer and helps match the person; it does not establish current employment at that domain."
        },
        "last_name": {
          "type": "string",
          "minLength": 1
        },
        "first_name": {
          "type": "string",
          "minLength": 1
        },
        "hashed_email": {
          "type": "string",
          "minLength": 1,
          "description": "Optional nonempty string containing an MD5 or SHA-256 hash of the known person’s email. It is a matching input, not a request to recover the email address or access a mailbox."
        },
        "linkedin_url": {
          "type": "string",
          "minLength": 1
        },
        "organization_name": {
          "type": "string",
          "minLength": 1
        },
        "reveal_phone_number": {
          "type": "boolean",
          "description": "Optional boolean requesting available phone data. Phone processing can be asynchronous, and returned numbers, arrival and completion time are not guaranteed. A pending request is not a completed phone result. The example explicitly sets false."
        },
        "reveal_personal_emails": {
          "type": "boolean",
          "description": "Optional boolean requesting available personal emails. Results depend on Apollo’s coverage and regional restrictions; an address is not guaranteed. The example explicitly sets false."
        }
      },
      "description": "Person-identifying information for matching one known person, such as an existing Apollo person ID, known email or LinkedIn profile, or a name with employer context. More relevant information can improve matching. Personal-email and phone request flags do not identify the person.",
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

When the main profile and an associated contact show different names or roles, keep their details separate rather than assuming they identify the same person. If financial figures are returned without a currency, leave the currency unspecified.

Official Apollo documentation

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

Use a known email, a public LinkedIn profile link, or a full name with a company name or website. The company may be a current or past employer.

Apollo Email Lookup for One Person

Apollo Email Lookup for One Person

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Connect your AI assistant

Use an email or LinkedIn profile

Help Apollo match a name

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Connect your AI assistant

Use an email or LinkedIn profile

Help Apollo match a name

Questions about this tool.

What details can I provide?

Will Apollo always find the right person?

Will this request a personal email or phone number?