Push GitHub Leads to Gong.io: Enrich Revenue Intelligence with Developer Signals

Gong.io captures what happens in sales calls. GitLeads captures what developers do on GitHub before they ever talk to sales. Combining the two gives your team revenue intelligence with developer-intent context — so reps walk into calls knowing a prospect starred your repo, filed an issue about a pain point you solve, or mentioned your competitor in a discussion thread.

Why Gong Needs GitHub Signal Context

Gong analyzes conversations after they happen. But the best sales conversations start with context before the call. When a developer stars your SDK, opens an issue asking about enterprise features, or mentions a keyword like "migrate from X to Y" — that is buying signal. Pushed into Gong as contact context, it changes how your reps open calls, what questions they ask, and how they frame value.

How GitLeads Routes GitHub Signals to Gong

GitLeads monitors GitHub in real time — new stargazers on tracked repos, keyword mentions in issues, PRs, discussions, and commit messages. When a signal fires, GitLeads enriches the profile: name, email (if public), GitHub username, company, location, followers, top languages, and signal context. That enriched lead then flows into Gong through one of three paths:

1. Direct webhook → Gong Calls/People API to create or update a person record with signal context
2. Via Zapier or Make: GitLeads webhook → Zapier → Gong (no custom code required)
3. Via CRM bridge: GitLeads → HubSpot/Salesforce → Gong sync (uses your existing CRM as source of truth)

Webhook Integration: GitLeads to Gong API

Gong's People API lets you create or update contact records. Here is a minimal TypeScript handler that receives a GitLeads webhook and upserts a Gong person with GitHub signal notes:

import type { Request, Response } from 'express';

interface GitLeadsWebhookPayload {
  type: 'stargazer' | 'keyword';
  signal: {
    repoFullName?: string;
    keyword?: string;
    contextUrl: string;
    contextTitle: string;
  };
  lead: {
    githubUsername: string;
    name: string | null;
    email: string | null;
    company: string | null;
    bio: string | null;
    followers: number;
    topLanguages: string[];
    profileUrl: string;
  };
}

async function upsertGongPerson(
  lead: GitLeadsWebhookPayload['lead'],
  signalNote: string
) {
  const credentials = Buffer.from(
    `${process.env.GONG_ACCESS_KEY}:${process.env.GONG_SECRET}`
  ).toString('base64');

  const res = await fetch('https://us-66051.api.gong.io/v2/people', {
    method: 'POST',
    headers: {
      Authorization: `Basic ${credentials}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      firstName: lead.name?.split(' ')[0] ?? lead.githubUsername,
      lastName: lead.name?.split(' ').slice(1).join(' ') ?? '',
      emailAddress: lead.email,
      title: lead.bio ?? undefined,
      companyName: lead.company ?? undefined,
      additionalData: {
        githubProfile: lead.profileUrl,
        githubSignal: signalNote,
        topLanguages: lead.topLanguages.join(', '),
        followers: lead.followers,
      },
    }),
  });

  if (!res.ok) throw new Error(`Gong API error: ${res.status}`);
  return res.json();
}

export async function handleGitLeadsWebhook(req: Request, res: Response) {
  const payload = req.body as GitLeadsWebhookPayload;
  const { lead, signal, type } = payload;

  const signalNote =
    type === 'stargazer'
      ? `Starred ${signal.repoFullName} on GitHub: ${signal.contextUrl}`
      : `Mentioned "${signal.keyword}" in: ${signal.contextTitle} — ${signal.contextUrl}`;

  await upsertGongPerson(lead, signalNote);
  res.status(200).json({ ok: true });
}

CRM Bridge: The Simpler Path

Most teams already sync their CRM to Gong. In that case, the easiest path is: GitLeads → HubSpot or Salesforce (via native integration) → Gong picks up contact records automatically. No custom code needed. The signal context lands in the contact notes field and surfaces in Gong's pre-call briefing.

Zapier / Make Automation (No-Code Path)

• Trigger: GitLeads webhook (new lead)
• Action 1: Search Gong for existing person by email
• Action 2: Create or update Gong person with GitHub signal note
• Optional: Notify sales rep via Slack with signal summary

What Your Reps See in Gong

With this integration active, when a developer who starred your repository or mentioned a buying keyword schedules a call, Gong surfaces their GitHub activity in the pre-call prep view. Reps see: what repo they starred, what issue they opened, what language they code in, and how many developers follow them on GitHub. That context changes the conversation from cold to warm in the first 30 seconds.

Signal Types That Work Best for Gong Enrichment

• Stargazer signals: developer starred your product or competitor repo — indicates evaluation or awareness
• Issue keyword signals: developer mentioned "pricing", "enterprise plan", "migrate from X" — indicates active consideration
• Discussion signals: developer asked about use cases, integrations, or roadmap — indicates deeper intent
• Code signals: developer referenced your library or pattern in commits — indicates active adoption