Twitter (X) to Email Finder — Email & LinkedIn by Handle avatar

Twitter (X) to Email Finder — Email & LinkedIn by Handle

Pricing

from $8.00 / 1,000 email founds

Go to Apify Store
Twitter (X) to Email Finder — Email & LinkedIn by Handle

Twitter (X) to Email Finder — Email & LinkedIn by Handle

Turn X (Twitter) handles into email addresses on record: work and personal emails with LinkedIn profile URL, name, job title and company. Twitter to email lookup in bulk from a database, no login. $8 per 1,000 found; misses and people with no email address on record are free.

Pricing

from $8.00 / 1,000 email founds

Rating

0.0

(0)

Developer

B2B Enrich Search

B2B Enrich Search

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 hours ago

Last modified

Share

What does Twitter (X) to Email Finder do?

Twitter (X) to Email Finder takes a list of X (Twitter) handles and returns the email address on record for the person behind each one, together with their name, job title, current company, location and LinkedIn profile URL. It is a Twitter to email lookup for sales, recruiting and CRM enrichment.

  • One narrow row per entry: the email address you asked for and just enough of the person's card to recognise them.
  • You pay only when the email address is found. A miss, a person with no email address on record, a removed profile and an invalid entry are free rows that say why.
  • Up to 1,000 entries per run, from the form, the API or an MCP client.
  • A database lookup. Nothing is crawled while your run is in progress, and no login, cookies or API key are needed.
  • Contact data, handled plainly. Every address is labelled work or personal; nothing is pattern-generated by this Actor.

What data do you get from an X (Twitter) handle?

FieldExampleNotes
_statusfoundfound, no_email, not_found, ambiguous, profile_removed, invalid, paused, error
_input{"twitter": "janedoe"}the entry as it was looked up
primaryEmailjane.doe@acme-example.comthe best address on record: current employer first, then personal, then other company domains
primaryEmailTypeworkwork or personal
employerMatchtruewhether an address sits on the current employer's domain
workEmails["jane.doe@acme-example.com"]every address on a company domain
personalEmails["jane.doe.example@gmail.com"]every address on a consumer mailbox provider
emailCount2addresses on the row
linkedinUrlhttps://www.linkedin.com/in/jane-doe-exampleon every found row
fullNameJane Doewhen on record
jobTitle, companyVP Marketing, Acme Examplecurrent role, when on record
location, countryAustin, Texas, United States, USwhen on record
_freshnessfresh_90dfresh_90d, updated_1y, older, or unknown when the record carries no date
_matchCandidates3only on ambiguous rows
_errora plain sentence on every row that is not found

How to convert Twitter to email (3 steps)

  1. Paste your X (Twitter) handles, one per line.
  2. Press Start and wait for the run to finish.
  3. Export the dataset as CSV, Excel or JSON, or read it through the API.

How much does Twitter to email cost?

EventPriceWhen
Email found$0.008 ($8 per 1,000)the entry resolved to one person and the row carries the email address
Everything else$0no match, a match with no email address on record, several people on one X (Twitter) handle, removed profile, invalid entry

A small per-run start fee may apply; it is shown on the Pricing tab.

Input

{
"handles": [
"@janedoe",
"https://x.com/samrivera"
]
}

A bare handle, an @handle, and profile links on x.com, twitter.com and mobile.twitter.com are all read as the same account. Handles are case-insensitive. Links to a page of the network (search, home, numeric i/user ids) are refused for free.

Output

A found row (charged):

{
"_status": "found",
"_input": {
"twitter": "janedoe"
},
"_freshness": "updated_1y",
"primaryEmail": "jane.doe@acme-example.com",
"primaryEmailType": "work",
"employerMatch": true,
"workEmails": [
"jane.doe@acme-example.com"
],
"personalEmails": [
"jane.doe.example@gmail.com"
],
"emailCount": 2,
"linkedinUrl": "https://www.linkedin.com/in/jane-doe-example",
"fullName": "Jane Doe",
"jobTitle": "VP Marketing",
"company": "Acme Example",
"location": "Austin, Texas, United States",
"country": "US"
}

A free row:

{
"_status": "no_email",
"_input": {
"twitter": "janedoe"
},
"_error": "A person matches this X (Twitter) handle, but no email address is on record for them. Not charged."
}

Twitter to email API, MCP and integrations

Run it from the Apify API, from the Apify MCP server in an AI assistant, or from Make, n8n and Zapier through their Apify connectors. The input is one array and the output is one flat row per entry, so it maps onto a spreadsheet column without reshaping.

Use cases

  • Sales and RevOps: add an email to leads that arrived with only an X (Twitter) handle.
  • Recruiting: reach a candidate you know only by an X (Twitter) handle.
  • Marketing: enrich a community, follower or signup list with professional context.
  • Developers and AI agents: one call in, one flat row out.

FAQ

How do I find an email from an X (Twitter) handle?

Paste the entry into the input and start the run. If it is on record for one person and that person has an email address on record, the row comes back found with it.

What is the match rate for Twitter to email?

About 18% of handles on a cold list resolve to a person: 43 of 241 developer handles in our test sample (2026-09-30). Of the people a handle resolves to, nearly all have an email on record (43 of 43 in the same sample). Your list may do better or worse. Because a lookup with nothing to return costs nothing, a test run on your own list costs only what it finds.

Am I charged when nothing is found?

No. Every row that is not found is free, including a person who matched but has no email address on record.

What happens when several people share one entry?

We cannot tell which of them you mean, so the row is marked ambiguous with the number of candidates and is not charged.

Can I run Twitter to email in bulk?

Yes: up to 1,000 entries per run, or send them as a JSON array through the API and split larger lists into several runs.

Does it need cookies, login or an API key?

No. The Actor reads from our own database and never logs in to any network.

How fresh is the data?

Each found row carries _freshness: fresh_90d (record updated within 90 days), updated_1y, older or unknown. People change jobs and contact details; check before you rely on a row.

That depends on what you do with the result and where you and the person are. Read "Disclaimer and permitted use" below.

NeedActor
Email → LinkedIn profile URLEmail to LinkedIn
Email → current company and job titleEmail to Company
Email → phone numbers on recordEmail to Phone
Email → X (Twitter) profileEmail to Twitter
Email → Facebook profileEmail to Facebook
Email → full professional profileReverse Email Lookup
LinkedIn URL → full profileProfile Lookup
LinkedIn URL → email addresses on recordLinkedIn Email Finder
LinkedIn URL → phone numbers on recordLinkedIn to Phone
X (Twitter) handle → emailTwitter to Email (this Actor)
X (Twitter) handle → LinkedIn profileTwitter to LinkedIn
Facebook profile → emailFacebook to Email
Facebook profile → phone numbers on recordFacebook to Phone
Facebook profile → LinkedIn profileFacebook to LinkedIn
GitHub username → emailGitHub to Email
GitHub username → LinkedIn profileGitHub to LinkedIn
Name + company domain → work emailWork Email Finder
Name + company domain → LinkedIn profileName to Profile
Handle on any of three networks → full profileSocial Handle Lookup
Company domain → company recordDomain to Company
Company domain → decision makersDomain to Decision Makers
Company domain → current employeesCompany Employees
Company domain → former employeesFormer Employees Finder
Filters → list of peoplePeople Database Search
Filters → list of companiesCompany Database Search
CSV of emails, URLs or names → profiles in bulkBulk People Enrichment

Disclaimer and permitted use

Independent product. This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation or X Corp. (X, formerly Twitter). LinkedIn®, X® and Twitter® are trademarks of their owners and are named here only to describe the kind of public profile link this Actor accepts or returns.

No platform access. This Actor does not log in to or crawl any of these services. Every answer comes from our own database of business-contact records. It never returns passwords, direct messages, or content from accounts that are not public.

Permitted use. Business-to-business purposes only: sales prospecting, recruiting outreach, CRM enrichment, and checking that a business contact is who they say they are. You may not use this Actor or its output to:

  • stalk, harass, threaten, dox or publicly expose any person;
  • identify the person behind a pseudonymous or non-professional account;
  • decide on anyone's eligibility for credit, employment, housing or insurance. This Actor is not a consumer reporting agency and its output is not a consumer report under the U.S. Fair Credit Reporting Act;
  • send unsolicited bulk messages, or place autodialed or prerecorded calls or texts without the consent the law requires;
  • profile people by health, religion, political opinion, sexual orientation, ethnicity or union membership;
  • build or resell a contact database from the results.

Your responsibilities. You decide whom to look up and what to do with the result. You are responsible for having a lawful basis for that use and for complying with the laws that apply to you, including GDPR and UK GDPR, ePrivacy and PECR, CCPA/CPRA, CAN-SPAM, and the TCPA and Do Not Call rules. Honor every opt-out you receive.

Removal requests. To have a person's data removed, open an issue on this Actor with only the profile link. Nothing else is needed, and the record is removed from every listing.

Accuracy. Records can be incomplete or out of date. Output is provided as is. Check it before you rely on it.