Push GitHub Leads to Greenhouse

Technical recruiters spend hours sourcing engineers on LinkedIn. GitHub is a better signal source: developers who star a repo related to your tech stack, contribute to open source in your domain, or discuss specific tools in issues are showing intent. GitLeads captures those signals and can push them into Greenhouse so your recruiting team works warm leads, not cold lists.

Why GitHub Signals Beat LinkedIn for Technical Recruiting

• Activity is public and verifiable — you see what they actually work on
• Signals are time-stamped — a recent star or PR is a live signal, not stale profile data
• Tech stack is implicit — language usage, repos contributed to, tools starred
• Community context — followers, stars received, discussions participated in
• No opt-in required — the signal is already public on GitHub

GitLeads to Greenhouse: The Integration Architecture

GitLeads does not have a native Greenhouse connector, but the webhook + Zapier or n8n route is straightforward. Here is the data flow:

GitHub Activity
  → GitLeads captures signal (star / keyword match)
  → GitLeads enriches: name, email, company, bio, top languages
  → GitLeads fires webhook payload

Webhook Payload (JSON):
{
  "username": "janesmith",
  "name": "Jane Smith",
  "email": "jane@example.com",
  "company": "Acme Corp",
  "bio": "Platform engineer | Go, Kubernetes, Rust",
  "location": "Berlin",
  "followers": 840,
  "topLanguages": ["Go", "Rust", "TypeScript"],
  "signalType": "stargazer",
  "signalRepo": "your-org/your-oss-repo",
  "signalAt": "2026-05-09T10:22:00Z"
}

→ Zapier / n8n receives webhook
→ Creates Greenhouse Prospect in target job pool

Setting Up via Zapier

1. In GitLeads, go to Integrations → Webhook and copy your webhook endpoint URL
2. Create a Zap with trigger: "Webhooks by Zapier → Catch Hook"
3. Add action: "Greenhouse → Create Prospect"
4. Map fields: first_name, last_name, email from webhook payload
5. Add custom fields for GitHub URL, signal type, and top languages
6. Set job pool or requisition based on `topLanguages` or signal context
7. Activate and test with a live GitLeads signal

Setting Up via n8n

// n8n Webhook → Greenhouse workflow

// Node 1: Webhook trigger (receives GitLeads payload)
// Node 2: Filter — only process signals with public email
// Node 3: HTTP Request to Greenhouse Harvest API

const greenhousePayload = {
  first_name: `${$json.name?.split(' ')[0]}`,
  last_name: `${$json.name?.split(' ').slice(1).join(' ')}`,
  email_addresses: [{ value: $json.email, type: 'personal' }],
  social_media_addresses: [
    { value: `https://github.com/${$json.username}`, type: 'github' }
  ],
  notes: `GitLeads signal: ${$json.signalType} on ${$json.signalRepo} at ${$json.signalAt}
Bio: ${$json.bio}
Company: ${$json.company}
Top languages: ${$json.topLanguages?.join(', ')}`,
};

// POST to: https://harvest.greenhouse.io/v1/prospects
// Headers: Authorization: Basic <base64(API_KEY:)>

What Signal Types to Track for Recruiting

• Stargazers on your company's open source repos — they know your product
• Contributors to repos you depend on — domain experts in your stack
• Keyword matches: "open to opportunities" or "looking for work" in GitHub bios or discussions
• Engineers starring repos in your tech domain (e.g., Kubernetes operators if you're hiring SREs)
• Maintainers of popular libraries in your stack — high-signal senior engineers

Filtering Signals Before They Hit Greenhouse

• Require public email — prospects without email cannot be contacted
• Minimum follower threshold (e.g., > 50) to filter hobbyists from professionals
• Language match — only route signals matching your hiring stack
• Company domain exclusion — skip employees at firms you do not recruit from
• Dedup by email — Greenhouse rejects duplicate email addresses