Push GitHub Leads to Chili Piper

Why GitHub Signals and Chili Piper Belong Together

Chili Piper is built around one insight: speed-to-lead determines conversion. If a developer stars your repository at 2pm and your sales rep does not reach out until the following morning, that window of intent has closed. Combining GitLeads GitHub signal capture with Chili Piper instant meeting routing shortens that window to minutes.

GitLeads detects GitHub signals — new stargazers on your tracked repos, keyword mentions in issues and PRs — and pushes enriched lead profiles in real time. Chili Piper routes those leads to the right rep and enables instant booking. The combination is an inbound pipeline that runs without manual intervention.

How the GitLeads → Chili Piper Integration Works

GitLeads does not have a native Chili Piper connector, but the integration is straightforward through three paths:

Path 1: Via HubSpot

If you use HubSpot as your CRM, GitLeads pushes GitHub leads directly into HubSpot as new contacts. Chili Piper's HubSpot integration then applies your routing rules — territory ownership, account matching, round-robin — when that contact submits a form or visits your pricing page. The GitHub signal enriches the contact record so reps see what the developer starred before the call.

Path 2: Via Webhook + Chili Piper API

Configure a GitLeads webhook to POST lead data to your backend, then call the Chili Piper API to create a lead and trigger routing.

// Webhook handler: GitLeads → Chili Piper
import express from 'express';
import axios from 'axios';

const app = express();
app.use(express.json());

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

  // Only route high-signal leads (100+ followers)
  if (lead.followers < 100) return res.json({ skipped: true });

  await axios.post(
    'https://api.chilipiper.com/v1/leads',
    {
      email: lead.email,
      first_name: lead.name?.split(' ')[0] ?? '',
      last_name: lead.name?.split(' ').slice(1).join(' ') ?? '',
      company: lead.company,
      custom: {
        github_username: lead.github_username,
        github_signal: lead.signal,
        github_repo: lead.repo,
        github_followers: lead.followers,
        signal_context: lead.body,
      },
    },
    { headers: { Authorization: `Bearer ${process.env.CHILIPIPER_API_KEY}` } }
  );

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

Path 3: Via Zapier or Make

GitLeads supports Zapier and Make natively. Build a Zap: GitLeads New Lead → Filter (followers > 50) → Chili Piper Create Lead. No code required, and routing rules apply automatically based on your Chili Piper workspace configuration.

Routing Rules for GitHub Developer Leads

Chili Piper Distro routing rules become more powerful when the lead is enriched with GitHub context:

• Follower count > 500 → route to senior AE or founder-led sales; these are GitHub influencers whose trial shapes ecosystem opinion
• Company field matches known enterprise accounts → route to named account owner; bypass round-robin
• Signal type = stargazer on your own repo → highest intent; trigger immediate Slack alert alongside calendar link
• Signal type = keyword mention containing "pricing" or "enterprise" → instant routing, not drip enrollment
• Top languages = Java, Go, or .NET → route to rep covering enterprise developer personas
• Location matches a target territory → route to regional rep for localized outreach

What Reps See When the Meeting Books

Pass these GitLeads fields through your CRM to Chili Piper custom fields so reps arrive briefed:

• Signal type — "starred ultralytics/ultralytics" or "mentioned 'ONNX export' in issue #412"
• GitHub bio — "Computer Vision Engineer @ startup.io" gives instant persona context
• Top languages — Python-first developers are different buyers than Go or Java engineers
• Followers — proxy for seniority and influence in the developer community
• Signal timestamp — rep knows this lead is warm from activity within the last 24h