Push GitHub Leads to Salesgear

Why Salesgear for Developer Outreach?

Salesgear is a multi-channel sales engagement platform that handles email sequences, LinkedIn steps, and call tasks from a single interface. For developer-focused GTM teams, pairing Salesgear with GitHub intent signals from GitLeads creates a high-signal outbound motion: developers who star your competitor's repo or mention your keywords in GitHub Issues get enrolled in a Salesgear sequence automatically — no manual prospecting required.

How GitLeads + Salesgear Works

1. GitLeads monitors GitHub for developer buying signals: new stargazers on tracked repos, keyword mentions in Issues/PRs/Discussions, and commit message signals.
2. When a signal fires, GitLeads enriches the developer profile with name, email (if public), GitHub username, company, top programming languages, and the triggering signal context.
3. GitLeads delivers the enriched lead to your webhook endpoint.
4. A lightweight middleware function (or Zapier/n8n flow) calls the Salesgear API to create a prospect and enroll them in the appropriate sequence.
5. Your Salesgear sequence runs the outreach — GitLeads never sends email. You handle outreach with your existing stack.

Salesgear API Integration

Salesgear provides a REST API for creating prospects and adding them to campaigns. Here is a TypeScript webhook handler that receives a GitLeads payload and pushes the lead to Salesgear:

// app/api/webhooks/gitleads-salesgear/route.ts
import { NextRequest, NextResponse } from 'next/server';

const SALESGEAR_API_KEY = process.env.SALESGEAR_API_KEY!;
const SALESGEAR_BASE = 'https://app.salesgear.io/api/v1';
const SEQUENCE_ID = process.env.SALESGEAR_SEQUENCE_ID!;

interface GitLeadsPayload {
  signalType: 'stargazer' | 'keyword';
  repo?: string;
  keyword?: string;
  developer: {
    githubUsername: string;
    name?: string;
    email?: string;
    company?: string;
    location?: string;
    bio?: string;
    followers: number;
    topLanguages: string[];
  };
}

export async function POST(req: NextRequest) {
  const payload: GitLeadsPayload = await req.json();
  const { developer, signalType, repo, keyword } = payload;

  if (!developer.email) {
    return NextResponse.json({ skipped: 'no email' });
  }

  const signalNote = signalType === 'stargazer'
    ? `Starred ${repo} on GitHub`
    : `Mentioned "${keyword}" in a GitHub Issue/PR`;

  // Create or update prospect in Salesgear
  const prospectRes = await fetch(`${SALESGEAR_BASE}/prospects`, {
    method: 'POST',
    headers: {
      'x-api-key': SALESGEAR_API_KEY,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      first_name: developer.name?.split(' ')[0] ?? developer.githubUsername,
      last_name: developer.name?.split(' ').slice(1).join(' ') ?? '',
      email: developer.email,
      company: developer.company ?? '',
      location: developer.location ?? '',
      custom_fields: {
        github_username: developer.githubUsername,
        github_signal: signalNote,
        top_languages: developer.topLanguages.slice(0, 3).join(', '),
      },
    }),
  });

  const prospect = await prospectRes.json();

  // Enroll in sequence
  await fetch(`${SALESGEAR_BASE}/sequences/${SEQUENCE_ID}/prospects`, {
    method: 'POST',
    headers: {
      'x-api-key': SALESGEAR_API_KEY,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({ prospect_id: prospect.id }),
  });

  return NextResponse.json({ ok: true, prospect_id: prospect.id });
}

Setting Up GitLeads → Salesgear

1. **Get your Salesgear API key** — In Salesgear, go to Settings → API → Generate API Key. Copy the key and add it to your environment as SALESGEAR_API_KEY.
2. **Create a sequence in Salesgear** — Build a developer-focused email sequence. Step 1: introduction referencing their GitHub activity. Step 2: value-add resource (case study, integration guide). Step 3: follow-up. Note the sequence ID.
3. **Deploy the webhook handler** — Deploy the TypeScript handler above to Vercel, AWS Lambda, or any Node.js server. Note the endpoint URL.
4. **Configure GitLeads webhook** — In GitLeads Settings → Integrations → Webhook, add your endpoint URL. GitLeads will POST each new developer lead here as JSON.
5. **Add repos and keywords to track** — In GitLeads, add GitHub repositories (yours and competitors') to monitor for stargazers. Add keywords to scan in GitHub Issues and PRs.
6. **Use custom fields for personalization** — In your Salesgear email templates, use the github_username and github_signal custom fields to personalize subject lines and openers.

Personalization With GitHub Signal Context

The github_signal custom field lets you write highly personalized email templates in Salesgear that reference the developer's actual GitHub behavior:

• Stargazer: "I noticed you starred {{repo}} on GitHub — we help teams evaluating {{category}}..."
• Keyword mention: "I saw your comment about {{keyword}} in a GitHub Issue — thought our approach might be relevant..."
• Language-based: "Given your background in {{top_languages}}, our {{feature}} might be a fit..."

Alternative: Use Zapier or n8n

If you prefer no-code, GitLeads supports Zapier and n8n natively. Create a Zap: trigger on GitLeads New Lead → action Create Prospect in Salesgear → action Enroll in Sequence. This eliminates the need for custom middleware while preserving the full signal context.