Push GitHub Leads to Clari

Why GitHub Signals Belong in Clari

Clari is where revenue teams inspect pipeline, call forecast, and track deal health. If you sell to developers, GitHub signals — a new star on your repo, a keyword mention in an issue, a competitor repo watcher — are early-stage buying indicators. Getting them into Clari surfaces intent data alongside CRM activity so your team can spot which deals have real developer engagement and prioritize accordingly.

GitLeads captures GitHub signals in real time and routes enriched lead profiles into Clari via HubSpot, Salesforce, or webhook — whichever CRM drives your Clari sync.

How the Integration Works

Clari reads from your CRM (HubSpot or Salesforce). The GitLeads to Clari pipeline is a two-step flow: GitLeads detects a GitHub signal and enriches the developer profile, then pushes it to HubSpot or Salesforce as a Contact with an Activity note. Clari syncs the CRM record and surfaces it in pipeline, deal rooms, and activity feeds.

Setting Up the GitLeads to Clari Pipeline

// GitLeads webhook → HubSpot → Clari
interface GitLeadsPayload {
  username: string;
  name: string;
  email: string | null;
  company: string | null;
  bio: string | null;
  followers: number;
  signalType: 'star' | 'keyword';
  signalContext: string;
  repo: string;
}

async function routeToHubSpot(lead: GitLeadsPayload) {
  const contact = await hubspot.crm.contacts.basicApi.create({
    properties: {
      email: lead.email ?? `${lead.username}@github.noemail`,
      firstname: lead.name?.split(' ')[0] ?? lead.username,
      lastname: lead.name?.split(' ').slice(1).join(' ') ?? '',
      github_username: lead.username,
      github_signal: lead.signalType,
      github_signal_context: lead.signalContext,
      github_repo: lead.repo,
      company: lead.company ?? '',
      hs_lead_status: 'NEW',
    }
  });

  // Activity note surfaces in Clari deal rooms
  await hubspot.crm.engagements.basicApi.create({
    engagement: { active: true, type: 'NOTE' },
    associations: { contactIds: [Number(contact.id)] },
    metadata: {
      body: `GitHub Signal: ${lead.signalType} on ${lead.repo}\n${lead.signalContext}`
    }
  });
}

What Clari Users See from GitHub Signals

• New Contact activity in deal rooms when a known account employee stars your repo
• Pipeline entries with GitHub signal context in HubSpot/Salesforce activity feed
• Signal timing data that helps Clari weight deal health and forecast calls
• "No activity" deals that suddenly show GitHub signal — Clari surfaces them for follow-up
• Developer intent signals enriching CRM records that were previously email-only

Best Signals to Route into Clari Pipeline

• Competitor repo stars — account you are pursuing is evaluating alternatives
• Keyword mentions ("pricing", "migrate from", "alternative to") — buying stage signal
• Stars from known account domains — existing deal gets new developer champion signal
• Stargazers with 500+ followers and engineer/CTO titles — high-influence developer signal
• Multiple signals from same company in 7 days — account heating up trigger for Clari