---
title: "Find Lead Emails and Phones From Claude or ChatGPT | traxy"
description: "Can Claude or ChatGPT find a verified work email for a LinkedIn lead? How to request email and phone lookups through the traxy MCP, and their limits."
canonical: "https://traxy.ai/blog/find-lead-emails-from-claude-chatgpt"
last_updated: "2026-11-12"
---

# Find Lead Emails and Phones From Claude or ChatGPT | traxy

> Can Claude or ChatGPT find a verified work email for a LinkedIn lead? How to request email and phone lookups through the traxy MCP, and their limits.

[Home](https://traxy.ai/) [Blog](https://traxy.ai/blog) [LinkedIn Lead Generation](https://traxy.ai/blog/topics/linkedin-lead-generation) 

Lead generation

# How to get work emails and phone numbers for LinkedIn leads from Claude or ChatGPT

Can Claude or ChatGPT find a verified work email for a LinkedIn lead? How to request email and phone lookups through the traxy MCP, and their limits.

By the traxy teamPublished Nov 12, 202613 min read

![How to get work emails and phone numbers for LinkedIn leads from Claude or ChatGPT — traxy blog](https://traxy.ai/assets/blog-covers/find-lead-emails-from-claude-chatgpt.jpg)

**In this article**[Can Claude or ChatGPT find a verified work email for a LinkedIn lead?](https://traxy.ai/blog/find-lead-emails-from-claude-chatgpt#can-claude-or-chatgpt-find-a-verified-work-email-for-a-linkedin-lead) [Why an AI chat can't find emails on its own](https://traxy.ai/blog/find-lead-emails-from-claude-chatgpt#why-an-ai-chat-can-t-find-emails-on-its-own) [Previewing and requesting a lookup through the traxy MCP](https://traxy.ai/blog/find-lead-emails-from-claude-chatgpt#previewing-and-requesting-a-lookup-through-the-traxy-mcp) [Auto-enrich for new leads, and looking up older ones](https://traxy.ai/blog/find-lead-emails-from-claude-chatgpt#auto-enrich-for-new-leads-and-looking-up-older-ones) [Saving an email or phone you already have](https://traxy.ai/blog/find-lead-emails-from-claude-chatgpt#saving-an-email-or-phone-you-already-have) [Permissions: contact scopes](https://traxy.ai/blog/find-lead-emails-from-claude-chatgpt#permissions-contact-scopes) [What a lookup can't promise](https://traxy.ai/blog/find-lead-emails-from-claude-chatgpt#what-a-lookup-can-t-promise) [From an email to LinkedIn and email outreach](https://traxy.ai/blog/find-lead-emails-from-claude-chatgpt#from-an-email-to-linkedin-and-email-outreach) [FAQ](https://traxy.ai/blog/find-lead-emails-from-claude-chatgpt#faq) [Open product docs](https://docs.traxy.ai/) 

**TL;DR: Not on their own. Claude and ChatGPT have no contact database to query, so a chat can guess an address but can't look one up or check it. Connect the traxy MCP and the same chat can preview and request an email or phone lookup for a lead in your traxy workspace, turn on automatic email enrichment for new leads, or queue email lookups for leads you already have, each after you confirm. A lookup can't guarantee that a usable address or number exists.**

traxy runs your entire LinkedIn GTM end to end, from finding high intent leads from social intent to enriching and researching each one, to running relevant, personalized LinkedIn and email outreach to them on autopilot. Autopilot here means a campaign runs on its own after you test it on sample leads and approve the launch, or you approve every message. This guide covers one step of that from an AI chat: getting a work email or phone for a lead.

If you want the general picture of email finders (what they return, how lookup works in the traxy app, and how name-plus-domain tools like Hunter and Snov.io compare), read [LinkedIn email finder: how to get a work email or phone for a LinkedIn lead](https://traxy.ai/blog/linkedin-email-finder)  first. This page is the AI-chat route: which traxy MCP tools Claude or ChatGPT calls, what you confirm, which scopes the connection needs, and what the lookup can't promise.

Last checked against the traxy docs: November 12, 2026.

## Can Claude or ChatGPT find a verified work email for a LinkedIn lead?

Not by themselves, but they can request one through the traxy MCP. Once traxy is connected, Claude or ChatGPT can preview a contact lookup for a lead in your workspace, request the email or phone lookup after you say yes, and read the saved result and its status.

Here is what the chat can do with the contact tools in the [traxy MCP tool catalog](https://docs.traxy.ai/api-reference/mcp/tools) :

-   `traxy_preview_lead_contact` previews a contact lookup for one lead, so you see what is already saved before you ask for more
    
-   `traxy_enrich_lead_contact` requests the lookup and reads the contact results traxy saved
    
-   `traxy_set_auto_enrich_email` turns automatic email enrichment on or off for leads delivered from then on
    
-   `traxy_backfill_lead_emails` queues email lookups for leads you already have
    
-   `traxy_set_lead_contact` saves an email or phone you already know, after `traxy_preview_set_lead_contact` shows the change
    

traxy's email lookup looks for a verified work email for the lead, and phone lookup looks for a phone number. Neither can promise a result. Check the saved status before you put an address in a sequence.

## Why an AI chat can't find emails on its own

An AI chat is good at reading, summarizing and drafting. Finding a contact detail is a different job: it needs a data source that holds contact records and a way to check them. A plain chat has neither.

Without a connected tool, here is what happens when you ask Claude or ChatGPT for someone's work email:

-   **It guesses a pattern.** The model may suggest firstname.lastname@company.com because many companies use a format like that. A guessed pattern is not a found address, and the chat has no way to tell you whether it would bounce.
    
-   **It searches the public web, if browsing is on.** It might find an address someone published on a website or in a press release. Most people don't publish their work email, so this often comes back empty or stale.
    
-   **It can state a wrong address with confidence.** A chat answer reads the same whether the model found the address or inferred it. You can't see the difference from the text alone.
    
-   **It doesn't know who is worth an email.** Even with a perfect address, a name from a title search is still a cold contact. The chat has no record of who engaged with what on LinkedIn or whether they fit your ICP.
    

The fix is to give the chat tools that reach real records. With the traxy MCP connected, the chat works on leads traxy already found and qualified, and it asks traxy to run the lookup. The chat stops guessing and starts reading saved results with a status.

Question

Chat on its own

Chat with the traxy MCP

Who should I contact?

Whoever you name, or a title search

High intent leads from LinkedIn social intent, each with a 50%+ ICP match and the post or comment behind them

Where does the email come from?

A guessed pattern or a public web page

traxy's email lookup, requested after you confirm

Can I check it?

Not from the answer

The result is saved on the lead with its status

What happens next?

You copy it somewhere

The lead can go into a LinkedIn and email campaign from the same chat

## Previewing and requesting a lookup through the traxy MCP

The short version: find the lead, preview the lookup, say yes, then read the result. Each lookup waits for your confirmation (unless you turn on automatic email enrichment). The traxy docs say contact lookup needs an explicit request, and a queued lookup is not proof that it finished.

### Step 1: Connect traxy to your AI chat

In traxy, open Integrations, pick your client, add `https://api.traxy.ai/api/v1/mcp`, sign in, pick the workspaces and approve. It is a one-time sign-in, with no API key needed. The same connection works in Claude, ChatGPT, Cursor, Codex and Grok. Setup details for each client are in [the AI clients docs](https://docs.traxy.ai/integrations/ai-clients) , and [the LinkedIn MCP page](https://traxy.ai/linkedin-mcp)  covers what the connection is for.

### Step 2: Start from a lead worth contacting

A lookup runs on a lead in your traxy workspace, so the first half of traxy decides who you look up. traxy finds high intent leads from LinkedIn social intent: people who post, comment on or like posts about the problem you solve, people who engage with competitors, creators, company pages or one post URL you track, and viewers of the sender accounts you connect. You can also search 71M+ scanned LinkedIn likes, posts and comments in plain English. A person counts as a lead only with a 50%+ match to your ICP, and every lead shows the post or comment behind it.

From chat, you can ask for those leads directly:

> Show five qualified leads from my workspace, with the post or comment behind each one.

For the full finding walkthrough in Claude, read [how to find and research LinkedIn leads from Claude with traxy](https://traxy.ai/blog/find-linkedin-leads-in-claude-traxy-mcp) .

### Step 3: Preview the lookup

Ask the chat to check what is saved before it requests anything:

> For the lead Jane Doe at Acme in my workspace, show which contact details are already saved. Don't request a lookup yet.

The chat calls `traxy_preview_lead_contact`. The traxy [contact details guide](https://docs.traxy.ai/leads/contact-details)  recommends reviewing the saved work email, personal email, phone and profile information before you request another lookup. If a work email is already there, you may not need a new one.

### Step 4: Confirm and request

When you want the lookup, say so plainly:

> Yes, request a work email lookup for that lead.

The chat calls `traxy_enrich_lead_contact`. You choose email, phone or both. A good habit is to tell the chat up front to ask before every lookup, for example: "Request a lookup only after I confirm."

### Step 5: Read the saved result and its status

Ask the chat to read the result back. A queued lookup is not proof of completion, so the chat should read the lead's current state before it repeats the request. If a work email came back, check its status. If nothing usable came back, keep the lead on LinkedIn or skip it.

### What about phone numbers?

Phone lookup works the same way from chat, with two conditions from the docs. It needs the phone add-on or an entitlement that includes it. And it applies to leads delivered after phone enrichment was activated: turning it on does not open phone lookups for older leads. The availability shown for each lead is the reference.

### Does a lookup use lead capacity?

No. Contact lookup does not use lead capacity and does not make the person a new qualified lead. That is different from starting a discovery run or qualifying a post's audience from chat, which asks you to confirm that new qualified people may use capacity.

## Auto-enrich for new leads, and looking up older ones

If you want an email lookup on every new lead without asking each time, turn on automatic email enrichment. If you want emails for leads you already have, queue a backfill. Both are available from chat.

### Turn on automatic email enrichment

> Turn on automatic email enrichment for my workspace. Tell me what changes before you do it.

The chat calls `traxy_set_auto_enrich_email`. What the docs say about how it behaves:

-   It starts off.
    
-   It applies to leads delivered after you turn it on. It does not backfill old leads.
    
-   Turning it off and on again starts a new boundary.
    
-   Contact details already saved stay available after you turn it off, while your workspace access lets you read them.
    

In the app, the same setting is under Auto-enrich in Leads, or Settings > Company > Lead enrichment.

### Queue email lookups for leads you already have

> Queue email lookups for my existing leads tagged "agency". Leave out leads marked Done. Show me the count first.

The chat calls `traxy_backfill_lead_emails`. The docs suggest you decide whether to include leads marked Done. As with single lookups, a queued backfill is not a finished one, so read the results before you build a list on them.

### Which one to use

You want

Use

Tool

One email or phone for one lead

A single lookup

`traxy_enrich_lead_contact`

An email lookup on every lead from now on

Automatic email enrichment

`traxy_set_auto_enrich_email`

Emails for leads you already have

A backfill

`traxy_backfill_lead_emails`

To store an email or phone you know

A manual save

`traxy_set_lead_contact`

Single lookups and export lookups don't require automatic enrichment to be on.

## Saving an email or phone you already have

Sometimes you already know the address: the person gave it on a call, or it is in your CRM. You can ask the chat to save it instead of running a lookup.

> Save jane@acme.com as the work email for Jane Doe. Show me the change first.

The chat calls `traxy_preview_set_lead_contact` to show the proposed value, then `traxy_set_lead_contact` after you approve. In the app, you can edit the field on the lead or ask trax, the traxy agent, to save it. What the docs say about manual details:

-   They are saved as unverified.
    
-   Enrichment won't overwrite them.
    
-   Entering a phone number does not need the phone add-on.
    
-   Clearing a manual value makes that field eligible for lookup again.
    
-   Future messages use the updated details. Records already delivered to an integration are not sent again automatically.
    

## Permissions: contact scopes

The chat can only do what your connection allows. When you connect, you sign in through the browser, select workspaces and approve the actions your account permissions allow. Each tool call has to satisfy the token scopes, the stored grant, your workspace membership, your role and your product access.

These are the scopes each contact tool needs, from the [MCP tool catalog](https://docs.traxy.ai/api-reference/mcp/tools)  and the [authentication and scopes](https://docs.traxy.ai/api-reference/authentication)  page:

Tool

Required scopes

`traxy_preview_lead_contact`

`leads:read`, `leads:contact_read`

`traxy_enrich_lead_contact`

`leads:contact_enrich`, `leads:read`, `leads:contact_read`

`traxy_set_auto_enrich_email`

`agent:run`

`traxy_backfill_lead_emails`

`agent:run`

`traxy_preview_set_lead_contact`

`leads:read`, `leads:contact_read`

`traxy_set_lead_contact`

`leads:manage`, `leads:contact_read`

Three things worth knowing:

-   **Reading leads is not reading contacts.** `leads:contact_read` is separate from `leads:read`. Without contact permission, contact fields and profile URLs are redacted.
    
-   **Refreshing doesn't add permissions.** OAuth refresh does not expand consent. To add a workspace or a permission, reauthorize.
    
-   **The catalog is not your grant.** The public catalog lists 234 tools before scope and workspace filtering. Ask the chat to run `tools/list` to see which tools your connection can use.
    

The REST API uses the same scope names on workspace API keys. The docs warn not to assume a key can read contact data because it can read leads, so check the scopes on each key. For every tool group and its scopes, see [what the traxy MCP server can do](https://traxy.ai/blog/traxy-mcp-server-capabilities) .

## What a lookup can't promise

The traxy docs are direct about this: a lookup is not a guarantee that a usable address or number exists. Plan for that.

-   **Some lookups come back empty.** Have a LinkedIn-only path for those leads.
    
-   **Check the status, not only the value.** Read the saved result and its status before you use it.
    
-   **Manual entries are unverified.** An address you typed in stays marked that way.
    
-   **Phone depends on access.** No phone add-on or entitlement means no phone lookup, and older leads stay out of scope.
    
-   **The chat can't make the data better.** Claude or ChatGPT only reports what traxy saved. If the chat states an address traxy didn't return, treat it as a guess.
    

We don't publish hit rates or accuracy percentages, and you should be wary of anyone who promises one for every lead. Measure bounces and replies on your own sends. For why some results come back empty, see [what is contact enrichment](https://traxy.ai/blog/what-is-contact-enrichment) .

### When a dedicated email finder fits better

If you already have a list of names and company domains and only need addresses, a name-plus-domain email finder is the direct tool, including in bulk. The [LinkedIn email finder guide](https://traxy.ai/blog/linkedin-email-finder)  compares two of them from their own pages. traxy fits when you don't have the list yet: you want the people showing interest on LinkedIn, checked against your ICP, then the contact details and the outreach in one place.

## From an email to LinkedIn and email outreach

An email is a way to reach someone, not a reason to. The reason is the LinkedIn activity behind the lead. Once a lead has a work email, the second half of traxy takes over, and you can run it from the same chat.

1.  Create a campaign for the leads, by signal, audience or offer. You can run many campaigns at once.
    
2.  traxy runs research on each lead for the facts you choose, filters out who doesn't fit and groups the rest by signal, and each group gets its own personalized message variant.
    
3.  traxy prepares a LinkedIn and email sequence that refers to the post or comment behind each lead.
    
4.  Test on sample leads with nothing sent, then review the launch: who joins, who is skipped, the sender, the steps and the delivery mode.
    
5.  Approve the launch and the campaign runs on its own, or approve each message in the review queue. From chat, the AI asks for your yes before anything sends or launches.
    
6.  Messages go out from your own connected sender accounts, LinkedIn accounts and mailboxes. Sending needs connected sender accounts.
    
7.  Replies, unsubscribes and hard bounces stop the sequence, and replies land in one inbox across LinkedIn and email.
    

Emails and LinkedIn profiles on your Do not contact list are kept out of outreach. For how campaigns work, see [LinkedIn outbound](https://traxy.ai/linkedin-outbound) .

## FAQ

### Can ChatGPT find a work email for a LinkedIn lead?

Not on its own. With the traxy MCP connected, ChatGPT can request an email lookup for a lead in your traxy workspace after you confirm, and read the saved result. The same works in Claude, Cursor, Codex and Grok.

### Will Claude look up emails without asking me?

The traxy docs say contact lookup needs an explicit request. Tell the chat to request a lookup only after you confirm, and review the preview first. Automatic email enrichment is the exception you choose: once you turn it on, new leads get an email lookup without a prompt.

### Does the traxy MCP return a phone number for every lead?

No. Phone lookup needs the phone add-on or an entitlement that includes it, applies to leads delivered after phone enrichment was activated, and can come back empty.

### Can I get emails for leads I found before I turned on auto-enrich?

Yes. Auto-enrich doesn't backfill, so ask the chat to queue email lookups for existing leads with `traxy_backfill_lead_emails`, and decide whether to include leads marked Done.

### Does looking up an email send anything?

No. A lookup stores contact data on the lead. Sending happens in a campaign or a one-off message from your connected sender accounts, after your approval.

### What permission does my AI client need to request a lookup?

`leads:contact_enrich`, plus `leads:read` and `leads:contact_read`. Turning on automatic email enrichment or queuing a backfill needs `agent:run`.

### How is this different from the LinkedIn email finder guide?

The [LinkedIn email finder guide](https://traxy.ai/blog/linkedin-email-finder)  explains email finders in general and how lookup works in the traxy app. This page covers doing it from an AI chat: the MCP tools, the confirmations and the scopes.

[Back to all articles](https://traxy.ai/blog) 

## Keep reading

[All LinkedIn Lead Generation guides](https://traxy.ai/blog/topics/linkedin-lead-generation) 

[Lead generation12 min read

## LinkedIn Lead Generation (2026): What It Is, Strategy, Tips and Tools for B2B

What LinkedIn lead generation is, a 7-step B2B strategy, the 5 main tactics, tips, tools and metrics, plus every LinkedIn lead generation guide we publish.

Updated Nov 12, 2026Read article](https://traxy.ai/blog/linkedin-lead-generation-guide-2026) [Lead generation15 min read

## LinkedIn GTM examples: real workflows, from profile viewers to campaigns run from Claude

Real LinkedIn GTM workflows, from profile viewers and old posts to campaigns run from Claude: what you set up, what traxy does and where you approve.

Updated Nov 13, 2026Read article](https://traxy.ai/blog/linkedin-gtm-examples) [Lead generation16 min read

## Are Your Buyers Active on LinkedIn? How to Check Before You Invest in LinkedIn Outreach

How to check if your buyers are active enough on LinkedIn before you invest in outreach: a one-hour test, signs to look for and who it is not a fit for.

Updated Nov 13, 2026Read article](https://traxy.ai/blog/are-your-buyers-active-on-linkedin) 

The right people are already out there.

## Find your warmest leads.  
_Send them personalized messages._

From relevant interest to personalized outreach.  
Put traxy to work.

[Start your free trial](https://app.traxy.ai/signup) [Book a demo](https://calendly.com/d/cvj3-p2p-cpv/traxy-demo?utm_source=website&utm_medium=cta&utm_campaign=book-demo&utm_content=footer) 

7-day free trial

[traxy](https://traxy.ai/) 

Get the most qualified leads on LinkedIn, in real time.

**Product**[Social Intent Search](https://traxy.ai/social-intent-search) [LinkedIn Social Listening](https://traxy.ai/linkedin-social-listening) [Signal-Based Outbound](https://traxy.ai/signal-based-outbound) [MCP Access](https://traxy.ai/linkedin-mcp) [Case Studies](https://traxy.ai/case-studies) [Pricing](https://traxy.ai/pricing) [DFY Outbound](https://traxy.ai/managed) 

**Resources**[Scoreboard](https://traxy.ai/scoreboard) [FAQ](https://traxy.ai/faq) [Guides](https://traxy.ai/guides) [Docs](https://docs.traxy.ai/) [Blog](https://traxy.ai/blog) [News](https://traxy.ai/news) [Affiliate ProgramNew](https://traxy.ai/affiliates) [Agency Partners](https://traxy.ai/agency) [Creators](https://traxy.ai/creators) [About traxy](https://traxy.ai/about) [Contact](https://traxy.ai/contact) 

**Legal**[Privacy Policy](https://traxy.ai/privacy-policy) [Terms of Service](https://traxy.ai/terms-of-service) [Cookie Policy](https://traxy.ai/cookie-policy) 

© 2026 traxy, inc. All rights reserved.
