GitHub to Email Finder — Deprecated

What does GitHub to Email Finder do?

GitHub to Email Finder takes a list of GitHub usernames 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 GitHub 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 a GitHub username?

Field	Example	Notes
_status	found	found, no_email, not_found, ambiguous, profile_removed, invalid, paused, error
_input	{"github": "janedoe"}	the entry as it was looked up
primaryEmail	jane.doe@acme-example.com	the best address on record: current employer first, then personal, then other company domains
primaryEmailType	work	work or personal
employerMatch	true	whether 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
emailCount	2	addresses on the row
linkedinUrl	https://www.linkedin.com/in/jane-doe-example	on every found row
fullName	Jane Doe	when on record
jobTitle, company	VP Marketing, Acme Example	current role, when on record
location, country	Austin, Texas, United States, US	when on record
_freshness	fresh_90d	fresh_90d, updated_1y, older, or unknown when the record carries no date
_matchCandidates	3	only on ambiguous rows
_error		a plain sentence on every row that is not found

How to convert GitHub to email (3 steps)

1. Paste your GitHub usernames, 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 GitHub to email cost?

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

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

Input

{
  "usernames": [
    "janedoe",
    "https://github.com/samrivera"
  ]
}

A username, an @username, or a github.com link (a repository link is read as its owner). Usernames are case-insensitive.

Output

A found row (charged):

{
  "_status": "found",
  "_input": {
    "github": "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": {
    "github": "janedoe"
  },
  "_error": "A person matches this GitHub username, but no email address is on record for them. Not charged."
}

GitHub 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 a GitHub username.
• Recruiting: reach a candidate you know only by a GitHub username.
• 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 a GitHub username?

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 GitHub to email?

About 18% of usernames on a cold list resolve to a person: 110 of 604 public developer accounts in our test sample (2026-09-30). Resolution is much higher for developers who list their LinkedIn profile on GitHub. Of the people a username resolves to, about 65% have an email on record (72 of 110). 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 GitHub 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.

Is it legal to look up an email this way?

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

Use GitHub to Email Finder with AI agents and MCP

This Actor works as a tool for AI agents. Add it to Claude, ChatGPT, Cursor or any other MCP client through the Apify MCP server:

https://mcp.apify.com?tools=b2bsearch/github-to-email

• Fast enough for a tool call. A small request finishes in seconds, so the agent gets its answer inside one call.
• The agent pays only for results. Prices are per result (see the pricing section above) and every miss is a free row. Cap what one call may spend with maxTotalChargeUsd.
• Rows explain themselves. Each row has a _status; a row that is not a result says why in _error, so the agent can decide what to do next without guessing.

Input an agent can send as is:

{
  "usernames": [
    "dhh"
  ]
}

The same Actor is available as a tool in LangChain, CrewAI and the OpenAI Agents SDK, and as a step in n8n, Make and Zapier through the Apify integrations.

Related Actors: which one should you use?

Need	Actor
Email → LinkedIn profile URL	Email to LinkedIn
Email → current company and job title	Email to Company
Email → phone numbers on record	Email to Phone
Email → X (Twitter) profile	Email to Twitter
Email → Facebook profile	Email to Facebook
Email → full professional profile	Reverse Email Lookup
LinkedIn URL → full profile	Profile Lookup
LinkedIn URL → email addresses on record	LinkedIn Email Finder
LinkedIn URL → phone numbers on record	LinkedIn to Phone
X (Twitter) handle → email	Twitter to Email
X (Twitter) handle → LinkedIn profile	Twitter to LinkedIn
X (Twitter) handle → phone numbers on record	Twitter to Phone
Facebook profile → email	Facebook to Email
Facebook profile → phone numbers on record	Facebook to Phone
Facebook profile → LinkedIn profile	Facebook to LinkedIn
GitHub username → email	GitHub to Email (this Actor)
GitHub username → LinkedIn profile	GitHub to LinkedIn
Name + company domain → work email	Work Email Finder
Name + company domain → LinkedIn profile	Name to Profile
Name + company domain → phone numbers on record	Name to Phone
Handle on any of three networks → full profile	Social Handle Lookup
Company domain → company record	Domain to Company
Company domain → decision makers	Decision Maker Finder by Domain
Company domain → current employees	Company Employees
Company domain → former employees	Former Employees Finder
Filters → list of people	People Database Search
Filters → leads with an email, from $1.50/1k	B2B Leads Finder
Filters → list of companies	Company Database Search
CSV of emails, URLs or names → profiles in bulk	Bulk People Enrichment

Free Apify plan

A run started from a free Apify plan delivers the first 100 results and stops; the run's status line says so. Any paid Apify plan lifts the cap. The rows are the same rows a paid run returns.

Feedback and reviews

How did it go? A rating in the Reviews tab of this Actor tells the next buyer what to expect; we read every word, good or bad. Got a wrong or stale row? Open the Issues tab with the run ID. Issues are public, so leave out emails, phones and names; the run ID is enough for us to find the row. We check every report, fix what is ours to fix and answer in the thread.

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 GitHub, Inc.. LinkedIn®, GitHub® 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.