GitHub Email & Lead Enricher — Devs to CRM Leads | Official API
Pricing
from $4.75 / 1,000 github leads
GitHub Email & Lead Enricher — Devs to CRM Leads | Official API
Turn GitHub users, orgs, repos or a search into enriched developer leads: email + company + location + hireable + followers + socials. Official API, no key required.
Pricing
from $4.75 / 1,000 github leads
Rating
0.0
(0)
Developer
Vitalii Bondarev
Maintained by CommunityActor stats
0
Bookmarked
4
Total users
3
Monthly active users
14 days ago
Last modified
Categories
Share
GitHub Email & Lead Enricher
Turn GitHub identifiers into enriched developer leads — not just an email, the whole lead record a sales/recruiting workflow needs.
What it does
Give it any mix of:
- usernames — GitHub logins to enrich directly
- orgs — enrich every public member of an organization
- repos (
owner/repo) — enrich a project's contributors - searchQuery — GitHub user-search, enrich the matches
…and for each developer it returns:
| field | notes |
|---|---|
email + email_source | profile email, or recovered from public commits when hidden (profile / commit / none) |
company, location, bio, blog, twitter_username | firmographic + contact context |
hireable | explicit "open to work" signal |
followers, following, public_repos, public_gists | lead-scoring metrics |
account_created_at, profile_updated_at, html_url | recency + navigation |
parse_confidence, warnings | a trust signal on each row (low = thin record) |
The wedge
Email-only competitors stop at {email, login, name}. This actor adds the
company / location / hireable / socials / scoring fields that make a row an
actual lead — and recovers the email from public commit history when the
profile hides it.
Access & cost
Official GitHub REST API — no key required. Supply a free githubToken to raise
the rate limit to 5000 req/hr; without one the actor rotates Apify Residential
proxy IPs to stay under the anonymous per-IP limit. Pay per lead
(github-lead event).
What "per lead" means for billing: you're charged once per person record returned — including leads where no public email could be recovered. Those records still carry name, company, location, bio, hireable, followers, and socials (a usable CRM lead), so they're billed the same. On a typical run roughly half to two-thirds of leads include an email; the rest are email-less but enriched. To keep only rows with an email, filter on
email != nulldownstream.
Notes
- Orgs are skipped from the output — leads are people, not organizations.
- Email recovery excludes GitHub's privacy
…@users.noreply.github.comaddresses. - All data is public; respect applicable laws when contacting leads.
