Push GitHub Developer Leads to LeadIQ

LeadIQ is a B2B prospecting platform that helps sales teams capture contacts, track job changes, and trigger outreach at the right moment. When you connect it to GitLeads, you get a feed of GitHub-native developer buying signals — stargazers, keyword mentions, repo contributors — that flow directly into LeadIQ as enriched contacts ready for sequencing.

Why Use GitLeads with LeadIQ

• LeadIQ excels at job-change tracking; GitLeads adds GitHub intent signals as a complementary trigger source
• Developers rarely appear in traditional B2B databases until they are already evaluating competitors — GitHub signals catch them earlier
• GitLeads provides GitHub-specific enrichment (top languages, starred repos, bio, follower count) that LeadIQ does not natively track
• Combine GitLeads signals with LeadIQ sequences for developer-specific outreach that references their actual GitHub activity
• No manual list building — signals flow in real time as developers star repos or mention keywords on GitHub

Integration Architecture: GitLeads → LeadIQ

LeadIQ does not expose a direct inbound lead creation API for external signals, so the integration uses one of two patterns: (1) GitLeads webhook → your backend → LeadIQ CSV import, or (2) GitLeads webhook → Zapier/Make → CRM sync → LeadIQ enrichment. The most common pattern for developer teams is the webhook-to-CRM approach, where GitLeads pushes to HubSpot or Salesforce and LeadIQ monitors those records for sequencing triggers.

Webhook Pattern: GitLeads → HubSpot → LeadIQ

// GitLeads webhook → HubSpot contact → LeadIQ enriches from CRM
import type { NextRequest } from 'next/server';

export async function POST(req: NextRequest) {
  const lead = await req.json();

  // Push enriched lead to HubSpot as a contact
  const response = await fetch('https://api.hubapi.com/crm/v3/objects/contacts', {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${process.env.HUBSPOT_TOKEN}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      properties: {
        email: lead.email,
        firstname: lead.name?.split(' ')[0] ?? '',
        lastname: lead.name?.split(' ').slice(1).join(' ') ?? '',
        company: lead.company ?? '',
        github_username: lead.githubUsername,
        signal_context: lead.signalContext,
        lead_source: 'GitLeads - GitHub Signal',
        top_language: lead.topLanguages?.[0] ?? '',
      },
    }),
  });

  // LeadIQ monitors HubSpot CRM and enriches/sequences from there
  return Response.json({ ok: response.ok });
}

Direct CSV Export Pattern

For teams that prefer LeadIQ's native CSV import workflow, GitLeads supports scheduled CSV exports of captured leads. Export your GitHub signal leads from GitLeads, format the CSV with email, first name, last name, company, and custom fields (GitHub username, signal context), then import into LeadIQ. LeadIQ will validate emails, de-duplicate against existing contacts, and make records available for sequence enrollment.

Personalizing LeadIQ Sequences with GitHub Context

• Use the signal context field to personalize first lines: "Noticed you starred {repo} last week..."
• Reference the developer's top programming language to show stack-level relevance in your pitch
• Include GitHub profile URL so SDRs can review the developer's actual work before reaching out
• Segment by signal type — stargazers get one sequence, keyword-match leads get a more targeted one
• Use LeadIQ's job-change trigger on top of GitLeads signals to catch developers who changed roles and are re-evaluating tools