Push GitHub Leads to Nimble CRM

Why Nimble CRM for GitHub Developer Leads

Nimble CRM is built for relationship-driven sales — it automatically enriches contact profiles with social data, tracks interactions, and surfaces insights for timely outreach. When you combine Nimble with GitLeads, every GitHub developer who stars your repo or mentions your keywords becomes an enriched contact in Nimble with full GitHub profile context, ready for personalized follow-up.

GitLeads captures buying signals from GitHub — new stargazers on tracked repos, keyword mentions in issues and PRs — and pushes them to Nimble via webhook or Zapier. The result: a steady feed of high-intent developer contacts, automatically enriched, in the CRM your team already uses.

What GitLeads Sends to Nimble

• GitHub username, display name, and public email address
• Bio, company name, and location from GitHub profile
• Follower count and top programming languages
• Signal type: stargazer event or keyword mention
• Signal context: repo starred or exact issue/PR text containing the keyword
• Signal timestamp for recency scoring in Nimble workflows

Integration Options: Webhook vs Zapier

Option A — Nimble API via GitLeads Webhook

// GitLeads webhook → Nimble API contact creation
// POST https://api.nimble.com/api/v1/contact

import express from 'express';
const app = express();

app.post('/gitleads-webhook', async (req, res) => {
  const lead = req.body;

  const nimblePayload = {
    fields: {
      'first name': [{ value: lead.github.name?.split(' ')[0] || lead.github.username, modifier: '' }],
      'last name': [{ value: lead.github.name?.split(' ').slice(1).join(' ') || '', modifier: '' }],
      email: lead.github.email ? [{ value: lead.github.email, modifier: 'work' }] : [],
      'company name': lead.github.company ? [{ value: lead.github.company, modifier: '' }] : [],
      URL: [{ value: lead.github.profileUrl, modifier: 'github' }],
      description: [{ value: `GitHub signal: ${lead.signalContext}`, modifier: '' }],
    },
    tags: ['github-lead', lead.signal.includes('star') ? 'stargazer' : 'keyword-signal'],
  };

  await fetch('https://api.nimble.com/api/v1/contact', {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${process.env.NIMBLE_API_KEY}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify(nimblePayload),
  });

  res.json({ ok: true });
});

Option B — Zapier Automation

1. In GitLeads: Settings → Integrations → Zapier → Copy webhook URL
2. In Zapier: New Zap → Trigger: Webhooks by Zapier → Catch Hook → paste URL
3. Add action: Nimble → Create Contact
4. Map fields: First Name → name (split), Email → email, Company → company, Tags → ["github-lead"]
5. Add a second Zapier step to add a note to the contact with signal context and repo name
6. Test with a live star event from GitLeads

Nimble Workflow for GitHub Developer Leads

• Tag contacts by signal type: "repo-star", "keyword-mention", "competitor-star"
• Use Nimble's Today Page to see GitHub leads surfaced as follow-up reminders
• Create a Nimble segment for "GitHub Lead" + "TypeScript" top language for targeted outreach
• Use Nimble's email tracking to see when GitHub leads open your messages
• Add contacts to Nimble sequences for developer onboarding or trial invite flows

Signal Types to Route to Nimble

• Stargazers on your own repos — warm leads who found your product organically
• Stargazers on competitor repos — discovery-stage developers evaluating alternatives
• Keyword signals: your product name, your category, or specific pain-point phrases in GitHub issues
• High-follower stargazers — influencers and community leaders worth prioritizing in Nimble