GitHub Followers Scraper — Export Developer Leads (Name · Company · Location · Email · X)

Turn any GitHub account's followers into an enriched developer lead list. This GitHub scraper takes any GitHub user or organization and exports everyone who follows them — each row enriched with name, bio, company, location, website, public email and X/Twitter handle. It is the fastest way to scrape GitHub followers and build a targeted list of real developers around a project, a tool, a competitor, or a thought leader — no login, no coding, no GitHub token required.

Export to JSON, CSV, Excel, or API.

🔓 Built for technical recruiters, dev-tool and SaaS marketers, DevRel and founders, and market researchers who need accurate, contactable developer audiences on demand.

---

🔎 Why scrape GitHub followers?

A GitHub account's followers are one of the highest-signal audiences on the internet. People who follow torvalds, vercel, or a popular framework's creator are, almost by definition, interested in that person, product, language, or ecosystem. That intent is exactly what makes GitHub follower data so valuable for recruiting, go-to-market, and research.

The problem is that GitHub gives you no export button. Follower lists are paginated an endless scroll at a time, and each profile hides the details you actually care about — the developer's real name, employer, location, personal website, and contact handles — behind a separate page visit. Collecting a few hundred by hand is tedious; collecting thousands across several accounts by hand is impossible. This GitHub followers scraper automates the whole pipeline: it walks the follower list page by page and enriches every single profile into one clean, spreadsheet-ready row.

Because the data is public profile information, you get a legitimate, repeatable way to map and reach developer communities without touching any private data or needing an API key.

Common reasons people scrape GitHub followers:

• 🧲 Build developer lead lists for recruiting or sales outreach from an account your ideal audience already follows.
• 🛠️ Reach a competitor's developer audience — the followers of a rival dev tool are the warmest possible market for yours.
• 🚀 Map and size a community around a framework, library, or company org.
• 📊 Find high-influence developers in a niche using their own follower counts.
• 🧑‍💻 Source engineers by company, location, and bio for technical hiring.
• 🤝 Research partnerships, sponsorships, and DevRel targets in a specific ecosystem.
• 📇 Enrich an existing contact list with website, X/Twitter, and public email.

---

✨ What this GitHub followers scraper does

• ✅ Scrapes followers of any user or organization — enter a person (torvalds), a company org (vercel), or a profile URL (https://github.com/microsoft). Add as many accounts as you like in one run.
• ✅ Enriches every follower profile — for each follower the GitHub scraper collects name, bio, company, location, website URL, public email, and X/Twitter handle, plus follower count, following count, avatar, profile URL, and account type.
• ✅ Automatic pagination — walks the GitHub followers list 100 records per page and returns hundreds to thousands of de-duplicated followers per account, controlled entirely by your maxItems and maxFollowersPerAccount limits.
• ✅ Works token-free — most competing GitHub scrapers force you to create API keys. This one runs out of the box; a free GitHub token is optional and only speeds up very large jobs.
• ✅ Per-account caps — keep results balanced when scraping several big accounts so one giant org doesn't eat your whole budget.
• ✅ Fast username-only mode — switch enrichment off for a quick list of handles, then re-enrich only the ones you care about.
• ✅ Clean, deduplicated, flat output — one row per follower, nulls dropped, ready for a spreadsheet or CRM.
• ✅ Multiple export formats — download as JSON, CSV, Excel, or XML, or pull via the Apify API and webhooks.
• ✅ Reliable at scale — datacenter proxy rotation plus automatic retries on rate limits (HTTP 403/429) keep large jobs running.

---

🎯 Use cases

• 🧲 Technical recruiters & tech sourcers — build candidate pipelines of engineers who follow a project, tool, or employer, then filter by location, company, and bio.
• 🛠️ Dev-tool & developer-platform marketers — reach the exact developers following a competitor or a complementary library.
• 🚀 Founders & DevRel teams — understand and re-engage your own (or a rival's) developer audience.
• 📊 Market & competitive researchers — map the community around a framework, SDK, or company and analyze it by company and geography.
• 🤝 Agencies & consultancies — assemble niche outreach lists of developers for clients.
• 📣 Developer-influencer & partnership scouts — use followersCount to spot high-reach developers for sponsorships and advocacy.
• 📇 Growth & RevOps teams — enrich account lists with contactable website and X/Twitter data.
• 🧪 Open-source maintainers — learn who follows your org and surface your most engaged community members.

---

📥 Input

Every input is optional — enter a GitHub account and press Start for a ready-made sample of ~100 enriched followers.

Field	Type	Description
usernames	array of strings	The GitHub users or organizations whose followers you want. Enter a username (torvalds) or a profile URL (https://github.com/vercel). Add as many as you like.
maxItems	integer	Stop after collecting this many followers in total across all accounts. Default 100. Set 0 for no limit.
maxFollowersPerAccount	integer	Optional cap per account — useful when scraping several accounts so one big account doesn't use your whole budget. 0 = no per-account cap.
enrichProfiles	boolean	On by default. Collects full profile details (name, bio, company, location, website, email, X/Twitter) for every follower. Turn off for a faster username-only list.
githubToken	string (secret)	Optional. Paste a free GitHub personal access token to run very large jobs faster and enrich via the GitHub API. Leave empty to run token-free.
proxyConfiguration	object	Recommended and on by default. Standard datacenter proxies are enough for this Actor.

Example input

{
  "usernames": ["yyx990803", "gaearon", "https://github.com/sveltejs"],
  "maxItems": 600,
  "maxFollowersPerAccount": 200,
  "enrichProfiles": true,
  "proxyConfiguration": { "useApifyProxy": true }
}

A minimal default-style run looks like this:

{ "usernames": ["torvalds"], "maxItems": 100 }

And a fast, username-only list (no enrichment) looks like this:

{ "usernames": ["kentcdodds"], "maxItems": 1000, "enrichProfiles": false }

---

📤 Output

Every follower is one flat, spreadsheet-ready row. Only the fields that exist for a given profile are included, so your export stays clean. Here is a real enriched row:

{
  "username": "dingyi",
  "name": "Ding Yi",
  "bio": "Independent designer & developer.",
  "company": "DEX",
  "location": "Remote",
  "websiteUrl": "http://ding.one/",
  "email": "dingyimac@gmail.com",
  "twitter": "dingyi",
  "followersCount": 378,
  "followingCount": 339,
  "avatarUrl": "https://avatars.githubusercontent.com/u/2486?v=4",
  "profileUrl": "https://github.com/dingyi",
  "type": "User",
  "followerOf": "yyx990803"
}

Field reference

Field	Description
username	🧑‍💻 The follower's GitHub username (login).
name	Their display name.
bio	Profile bio.
company	🏢 Company / organization, often an @handle.
location	📍 Self-reported location.
websiteUrl	🔗 Personal or company website from the profile.
email	✉️ Public email — present only when the user made it public.
twitter	🐦 X / Twitter handle.
followersCount	👥 How many followers they have — an influence signal.
followingCount	How many accounts they follow.
publicRepos	📦 Public repository count — present with GitHub token enrichment.
hireable	✅ Whether they flagged themselves open to work — present with token enrichment.
createdAt	🕒 When they joined GitHub — present with token enrichment.
avatarUrl	🖼️ Avatar image URL.
profileUrl	🔗 Link to their GitHub profile.
type	User or Organization.
followerOf	Which target account this person follows.

About coverage: identity fields — username, avatarUrl, profileUrl, type, followerOf — are present on 100% of rows. In the default token-free mode, name, location, followersCount, and followingCount are present on the large majority of profiles, while websiteUrl, bio, company, twitter, and email appear when the developer made them public (website and X/Twitter are common; public email is intentionally rare on GitHub). The publicRepos, hireable, and createdAt fields populate when you run with a GitHub token (the GitHub API path). This is honest, data-dependent behavior — not a bug.

---

🔁 Pagination & scale

The GitHub followers scraper paginates the GitHub followers list automatically. It requests 100 followers per page and advances page by page until it reaches your limit or the end of the account's follower list, so a single run can return hundreds to thousands of de-duplicated followers.

• Control total volume with maxItems (default 100, 0 = no limit).
• Control per-account volume with maxFollowersPerAccount to balance multi-account runs.
• Followers are de-duplicated within each account, so you never get the same person twice from one target.
• Per GitHub's own API, very large accounts are collected up to a high practical ceiling (~10,000 followers per account); use the caps to control size, speed, and cost.

Collection is backed by datacenter proxy rotation and automatic retries on rate limits (HTTP 403/429) — if GitHub throttles one IP, the Actor rotates and continues, so big jobs finish cleanly.

---

⚙️ How to use

1. Open the GitHub Followers Scraper on the Apify Console.
2. In GitHub accounts (usernames), type one or more usernames or paste profile URLs — e.g. torvalds, vercel, https://github.com/microsoft.
3. Set maxItems (and optionally maxFollowersPerAccount), and leave enrichment on for full profiles.
4. Press Start. Watch progress in the run log, then open the Output tab to preview results.
5. Export to Excel, CSV, JSON, or XML, or send the data to Google Sheets, Airtable, Zapier, Make, n8n, or your own app via the Apify API and webhooks.
6. Want it fresh? Add an Apify Schedule to re-run the GitHub scraper daily, weekly, or monthly.

---

💡 Tips

• 👤 Target the right account. The more focused the account, the more relevant its followers — a niche library beats a giant general org for precision.
• 🔢 Use a per-account cap when combining several big accounts so results stay balanced and your budget predictable.
• ⚡ Turn off enrichment (enrichProfiles: false) for a quick username-only list, then re-run enrichment on just the handles you care about.
• 🔑 Add a free GitHub token only for very large pulls — it speeds things up and unlocks publicRepos, hireable, and createdAt.
• 🧹 Dedupe across targets downstream if you scrape overlapping audiences (the Actor dedupes within each account).
• 📊 Sort by followersCount in your spreadsheet to surface the most influential developers first.

---

❓ FAQ

Is scraping GitHub followers legal? This GitHub scraper collects only publicly available profile information for legitimate research, recruiting, and lead generation. You are responsible for how you use the data, including compliance with GDPR, CCPA, platform terms, and anti-spam rules when contacting anyone. Don't use it for unsolicited bulk messaging.

Do I need a GitHub token or login? No. The Actor runs fully token-free and requires no login. A free GitHub personal access token is optional and only speeds up very large jobs (and adds a few extra fields).

How many followers can I scrape, and how fast? You can collect hundreds to thousands of followers per run. In token-free mode the Actor enriches around 100 followers in well under a minute; GitHub's practical ceiling is roughly 10,000 followers per account.

Do I need proxies? Proxies are recommended and on by default. Standard datacenter proxies are enough — no residential proxies required.

Which fields come back, and are emails always included? Every row has username, avatar, profile URL, type, and the target it follows. Name, location, and follower/following counts are present on most profiles. Website and X/Twitter are common; public email appears only when the developer made it public, so expect it on a minority of rows.

Can I scrape an organization's followers, not just a person's? Yes. GitHub lets people follow organizations, and this GitHub followers scraper collects org followers too.

Will I get duplicate followers? No. Followers are de-duplicated within each account automatically.

Is there an API, and what export formats are supported? Yes. Run it via the Apify API, and export results as JSON, CSV, Excel, or XML, or stream them to webhooks and tools like Make, Zapier, and n8n.

How fresh is the data? Every run scrapes GitHub live, so results reflect the current follower list and profiles. Schedule the Actor to keep your lists up to date.

Can I filter by location or company? The Actor returns location, company, bio, and other fields on every enriched row, so you can filter and segment your export by those columns in a spreadsheet, CRM, or script after the run.

---

🔗 Related scrapers

• GitHub Developer Scraper — search and enrich GitHub user and developer profiles.
• GitHub Repository Scraper — extract GitHub repositories with stars, topics, and metadata.
• GitHub Repo Audience Scraper — scrape the stargazers, forkers, and watchers of any repo.
• Product Hunt Launches Scraper — collect Product Hunt launches, makers, and engagement.
• WordPress Directory Scraper — scrape plugins and themes from the WordPress directory.
• npm Package Scraper — extract npm packages, maintainers, and download stats.

---

▶️ Ready to build your developer lead list? Enter a GitHub account and click Start to scrape GitHub followers now.