Push GitHub Leads to Kustomer

Why Push Developer Leads into Kustomer

Kustomer is a CRM and customer service platform that unifies customer data across conversations, support tickets, and sales touchpoints. Developer-focused companies using Kustomer can enrich their contact records with GitHub intent signals — the developer checked out a competitor repo, mentioned a pain point in a GitHub issue, or starred your OSS project. GitLeads captures these signals and pushes enriched lead profiles into Kustomer in real time.

What GitLeads Sends to Kustomer

Each GitLeads lead capture includes structured data ready for Kustomer contact creation:

• Full name and email address (when public on GitHub profile)
• GitHub username and profile URL
• Bio, company, and location from GitHub
• Follower count and top programming languages
• Signal context: which repo was starred, or which keyword was matched and where
• Timestamp of the signal event

Integration Path: GitLeads to Kustomer

Kustomer exposes a REST API for contact and conversation creation. GitLeads delivers leads via outbound webhook, making the integration straightforward via any automation layer. The recommended paths:

• GitLeads Webhook → Zapier → Kustomer: use the Kustomer Zapier app to create or update contacts from webhook payload fields
• GitLeads Webhook → n8n → Kustomer: build an n8n workflow using the HTTP node to POST to the /v1/customers endpoint
• GitLeads Webhook → Make → Kustomer: use the Make HTTP module to map lead fields to Kustomer customer attributes
• GitLeads Webhook → direct Kustomer API: POST to https://api.kustomerapp.com/v1/customers with the lead payload

Kustomer API: Creating a Contact from a GitHub Lead

Here is a minimal example of creating a Kustomer customer record from a GitLeads webhook payload:

// GitLeads webhook → Kustomer contact creation
interface GitLeadsPayload {
  name: string;
  email: string;
  githubUsername: string;
  company: string;
  bio: string;
  signalType: 'stargazer' | 'keyword';
  signalContext: string;
  capturedAt: string;
}

async function pushLeadToKustomer(lead: GitLeadsPayload) {
  const res = await fetch('https://api.kustomerapp.com/v1/customers', {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${process.env.KUSTOMER_API_KEY}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      name: lead.name,
      emails: lead.email ? [{ type: 'work', email: lead.email }] : [],
      urls: [{ url: `https://github.com/${lead.githubUsername}` }],
      company: lead.company,
      custom: {
        githubUsername: lead.githubUsername,
        bio: lead.bio,
        signalType: lead.signalType,
        signalContext: lead.signalContext,
        capturedAt: lead.capturedAt,
      },
    }),
  });
  return res.json();
}

Routing Leads to Kustomer Conversations

Beyond contacts, you can create Kustomer conversations for high-signal leads — for example, when a developer mentions a specific pain point keyword in a GitHub discussion. Use the POST /v1/conversations endpoint, associate it with the created customer, and assign it to the right sales or support queue. This lets your team action GitHub signal as an inbound-style conversation inside Kustomer.

Filtering Which Leads Go to Kustomer

Not every GitHub signal needs to go to Kustomer. Use GitLeads filtering to route only the most qualified leads: developer followers above a threshold, specific top languages (Go, Rust, Python), or signals from repos that indicate your ICP. Low-signal leads can route to a spreadsheet or Slack channel for review, while high-confidence matches go directly to Kustomer.