GitHub Email Scraper

🔍 GitHub Email Scraper – Overview

Looking for email addresses on GitHub? The GitHub Email Scraper searches public GitHub pages for the keywords you choose and saves every email address it finds, along with the title, description and link of the page. It is a fast GitHub email finder for B2B lead generation, sales, recruiting and outreach, and the GitHub Email Scraper needs no coding.

GitHub is the platform for hosting and sharing code, which makes it a useful place to look for founders, front-end developers and software engineers. With the GitHub Email Scraper there is nothing to install and no GitHub account to connect: start a run, wait for the dataset to fill, then export your email list as JSON, CSV or Excel. 📥 It works as an email finder and an email extractor in one.

✨ GitHub Email Scraper at a glance

• Platform: GitHub (github.com)
• What you get: public email addresses of founders, front-end developers and software engineers
• How you search: keywords, locations and email domains
• Data: email, page title, description, link and lead details
• Best for: B2B lead generation, prospecting and outreach
• Export: JSON, CSV, Excel or the Apify API

Whether you run the GitHub Email Scraper once for a quick list or on a schedule for ongoing GitHub lead generation, the settings stay the same, so results from different runs are easy to compare.

---

⭐ GitHub Email Scraper – Key Features

The GitHub Email Scraper is built for fast, repeatable GitHub lead generation:

• All-in-one email finder – the GitHub Email Scraper locates GitHub pages for your keywords and extracts the email addresses shown there, so the GitHub Email Scraper is both an email finder and an email extractor for GitHub.
• GitHub keyword search – run several keywords in one go, such as "Founder" and "Frontend Developer", and collect contact data for each.
• Location targeting – narrow results to a country, state or city, or add a list of extra locations that are each searched on their own.
• Email domain control – look for @gmail.com, @yahoo.com, @outlook.com or your own suffixes, accept any address, or keep business emails only.
• Must-include and exclude words – keep only results that mention the words you need and skip snippets with words you do not want.
• Limits that protect your budget – cap the emails per search combination and set one total limit for the whole run.
• Parallel searches – the GitHub Email Scraper can run up to 10 GitHub searches at the same time to finish long keyword lists sooner.
• Duplicate-free results – an email found by several searches is saved only once, so your email list stays clean.
• Do-not-contact list – keep opted-out addresses and existing contacts out of your dataset.
• Lead history – skip emails you already collected in earlier runs, so you only get new leads.
• Optional extras – add phone numbers shown in the result text and check email domains before saving.
• Resumable runs – an interrupted GitHub Email Scraper run continues from its saved progress instead of starting over.
• Only GitHub results – results from other websites are dropped, so every row links to a page on GitHub.
• Ready for your tools – send leads to a CRM, spreadsheet or automation through Apify integrations and webhooks.

---

📊 GitHub Email Scraper – What Data You Can Extract

The GitHub Email Scraper saves one row of GitHub contact data for every unique email address:

Field	What it contains
network	Source label, GitHub.com
keyword	The keyword that produced the result
title	Title of the result
description	Result text in which the email appeared
url	Link to the page
email	The email address
location	Location used for the search, or null
emailType	free for webmail providers, business for other domains
username	Handle or first path segment of the GitHub link, when it can be read
followersCount	Follower count if the result text shows one, otherwise null
influencerTier	Under 1K, Nano, Micro, Macro or Mega, from the follower count; null if unknown
emailStatus	Only with email verification: valid or unverified
phoneNumbers	Only with phone extraction: numbers found in the result text

💡 Good to know: the GitHub Email Scraper reads the public text shown for each GitHub result. Only email addresses that are visible there can be found, so results depend on what GitHub users publish.

---

🚀 GitHub Email Scraper – How to Use It

Getting your first GitHub email list with the GitHub Email Scraper takes only a few minutes:

• Step 1 – Open the Actor: open the GitHub Email Scraper in Apify Store and click Start.
• Step 2 – Add keywords: enter one or more GitHub search terms, for example "Founder".
• Step 3 – Set a location (optional): type a country or city such as San Francisco, or leave the field empty.
• Step 4 – Choose email types: keep @gmail.com or add other suffixes, or switch the email mode to any address or business emails only.
• Step 5 – Set limits: decide how many emails each combination may collect and, if you like, a total for the run.
• Step 6 – Run and export: start the GitHub Email Scraper, follow the dataset as it fills, then download JSON, CSV or Excel.

---

🎯 How to Extract GitHub Emails by Keyword and Location

Every GitHub keyword is combined with every location and every email suffix, and each combination is its own search with its own email target. Two keywords, three locations and two suffixes make 12 searches. With the GitHub Email Scraper, use the total limit to keep large GitHub runs predictable, and use the extra locations list to cover many cities, for example San Francisco, in a single run. A search for "Founder" in San Francisco is one combination, and "Frontend Developer" in San Francisco is another.

---

🧭 Can You Filter GitHub Email Scraper Results by Email Domain?

Yes. The email mode setting of the GitHub Email Scraper has three options:

• Only the domains listed – the default; finds exactly the suffixes you enter, such as @gmail.com.
• Any email address – accepts every address found in GitHub result text, whatever the domain.
• Business emails only – accepts any address except free webmail providers like Gmail, Yahoo or Outlook, which suits B2B outreach on GitHub.

The two broad modes find addresses a fixed list would miss, but expect fewer results per search and some noise.

---

💼 GitHub Email Scraper – Use Cases

Teams use the GitHub Email Scraper for:

• Developer recruiting – a ready email list of founders, front-end developers and software engineers that you can contact right away.
• Tool and API outreach – search "Founder" in San Francisco or any other place and compare the GitHub results by location.
• Open-source partnerships – export the contact data to your CRM, spreadsheet or B2B outreach tool.
• Finding maintainers – schedule the GitHub Email Scraper to keep your GitHub lead generation running.

Because the GitHub Email Scraper returns structured data, it fits manual research as well as automated lead generation and outreach pipelines.

---

⚙️ GitHub Email Scraper – Input

The GitHub Email Scraper accepts the fields below. Only keywords is required; every other field has a default.

Field	Type	Default	What it does
keywords	list	["Founder", "Frontend Developer", "Software Engineer"]	Keywords to look for, one per line. Each keyword runs on its own.
location	text	empty	Optional country, state or city added to every search.
locations	list	[]	Extra places, each searched separately with the same keywords.
emailSearchMode	text	domainList	Which emails to look for: your domain list, any address, or business emails only.
customDomains	list	["@gmail.com"]	Email suffixes to look for, such as @gmail.com or @yahoo.com.
maxEmails	number	5	Emails per search combination (keyword + location + domain). Free accounts: 100 at most.
maxTotalEmails	number	0	Hard stop for the whole run. 0 means no total limit.
maxConcurrentSearches	number	5	How many searches run at the same time (1 to 10).
minFollowers	number	0	Keep only results showing at least this many followers. 0 switches it off.
maxFollowers	number	0	Keep only results showing at most this many followers. 0 switches it off.
profilesOnly	true/false	false	Keep only results whose link looks like a single profile page.
includeWords	list	[]	A result is kept only if it contains at least one of these words.
excludeWords	list	[]	Results containing any of these words are skipped.
extractPhoneNumbers	true/false	false	Also return phone numbers written in the result text.
verifyEmails	true/false	false	Check format, placeholders and mail servers before saving an address.
skipPreviouslyFoundEmails	true/false	false	Skip addresses saved by earlier runs under the same history name.
historyStoreName	text	github-email-history	Name of the saved history (lowercase letters, numbers, hyphens).
excludeEmails	list	[]	Addresses or @domains that must never appear in the results.

🧪 Example input

{
  "keywords": ["Founder", "Frontend Developer"],
  "location": "San Francisco",
  "emailSearchMode": "domainList",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 20,
  "maxTotalEmails": 100,
  "maxConcurrentSearches": 5,
  "excludeWords": ["spam"]
}

---

📦 GitHub Email Scraper – Output

Results are written to the run's dataset as they are found, so you can watch the list grow. Each item contains the fields described above. A short run summary (unique emails, skipped results by reason, searches finished) is also stored with the run.

🧾 Example output

[
  {
    "network": "GitHub.com",
    "keyword": "Founder",
    "title": "Founder in San Francisco | GitHub",
    "description": "Example listing for Founder in San Francisco. Contact: sample.contact@gmail.com",
    "url": "https://github.com/sample_founder",
    "email": "sample.contact@gmail.com",
    "location": "San Francisco",
    "emailType": "free",
    "username": "sample_founder",
    "followersCount": null,
    "influencerTier": null
  },
  {
    "network": "GitHub.com",
    "keyword": "Frontend Developer",
    "title": "Second example result | GitHub",
    "description": "Another example description with sample.team@yahoo.com in the text.",
    "url": "https://github.com/sample_founder_2",
    "email": "sample.team@yahoo.com",
    "location": "San Francisco",
    "emailType": "free",
    "username": "sample_founder_2",
    "followersCount": null,
    "influencerTier": null
  }
]

The data above is example data that shows the structure of GitHub results.

---

💰 GitHub Email Scraper – Pricing

The GitHub Email Scraper uses Apify's pay-per-result model: you pay for the GitHub emails that are saved to your dataset. Duplicates, addresses removed by your filters and addresses that fail verification are not saved or charged.

• Keep costs predictable: set maxEmails, maxTotalEmails and the maximum cost of the run.
• Free Apify plans: up to 100 emails per search combination.
• Current rates: see the pricing information on the Actor page.

---

✅ GitHub Email Scraper – Tips and Best Practices

Get more from the GitHub Email Scraper with these habits:

• Use several specific keywords – instead of only one broad term, try close variations such as "Founder" and "Frontend Developer".
• Start small – run the GitHub Email Scraper with a low maxEmails first, check the results, then scale up.
• Loosen the search if results are sparse – add more email suffixes, more keywords or clear the location.
• Use include and exclude words – they keep the email list relevant and remove noise.
• Raise parallel searches – 5 to 10 searches at once finish long runs sooner.
• Use lead history for repeat runs – switch on skipping of earlier emails so each run returns new leads only and your outreach never repeats.
• Respect privacy rules – use the contact data responsibly and follow the laws and platform terms that apply to your outreach.

---

❓ GitHub Email Scraper – Frequently Asked Questions

💬 What is the GitHub Email Scraper?

It is an Apify Actor and email finder that extracts public email addresses from GitHub based on your keywords and saves them as structured data, ready for outreach.

💬 Who is the GitHub Email Scraper for?

It is for anyone who needs contact data for founders, front-end developers and software engineers: sales teams, recruiters, agencies and researchers. Typical goals are developer recruiting and tool and API outreach.

💬 How does the GitHub Email Scraper find emails on GitHub?

It searches public results for GitHub pages with each keyword and reads the email addresses shown in the result title and description. Results from other websites are skipped.

💬 Do I need to log in to GitHub to use the GitHub Email Scraper?

No. The GitHub Email Scraper works without any GitHub login or account.

💬 Can I extract GitHub emails for a specific city or country?

Yes. Use the location field for one place or the locations list for several, for example San Francisco. Each location is searched separately.

💬 What data does the GitHub Email Scraper return?

Each row has the email address, the keyword, the page title, description and link, the location, the email type and optional follower, phone and verification fields.

💬 Can the GitHub Email Scraper get phone numbers from GitHub as well?

Yes, optionally. Switch on phone extraction and the GitHub Email Scraper adds the numbers written in the result text to the phoneNumbers field.

💬 Why did my GitHub run return fewer emails than expected?

The GitHub Email Scraper can only find addresses that are publicly shown for GitHub results. Try more keywords, more email suffixes, a broader location or the any-address mode.

💬 How do I export GitHub emails to CSV or Excel?

Open the run's dataset and choose CSV, Excel or JSON, or fetch the email list through the Apify API.

💬 Is the GitHub Email Scraper an email finder or an email extractor?

Both. The GitHub Email Scraper finds GitHub pages for your keywords and extracts the email addresses shown there, so it works as an email finder and an email extractor for GitHub.

---

🤝 Support

Questions, ideas or a custom scraper for GitHub? The GitHub Email Scraper is actively maintained, so get in touch:

• contact me by email : alphascraper69@gmail.com