Push GitHub Leads to Common Room

Why Common Room for GitHub Lead Intelligence

Common Room is a developer community intelligence platform that aggregates signals from GitHub, Slack, Discord, LinkedIn, and other channels into unified member profiles. When you push GitLeads data into Common Room, you combine real-time GitHub intent signals — stargazers, keyword mentions in issues and PRs — with the full community engagement history Common Room already tracks. A developer who mentioned your competitor in a GitHub issue AND has been active in your Discord for 90 days is a fundamentally different prospect than a cold lead, and Common Room surfaces that distinction.

What GitLeads Adds to Common Room

Common Room natively tracks GitHub activity for your own repos, organization members, and direct community signals. What it does not capture is outbound GitHub monitoring — signals from repos you do not own, competitor stars, or keyword mentions across the broader GitHub ecosystem. GitLeads fills that gap. By pushing GitLeads webhook payloads to Common Room via its API, you enrich member profiles with new buying signals the moment they fire.

// Push a GitLeads signal to Common Room member profile
// POST /api/gitleads-to-common-room

export async function POST(req: Request) {
  const lead = await req.json();

  // Common Room API — create or update a member
  const response = await fetch('https://api.commonroom.io/community/v1/members', {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${process.env.COMMON_ROOM_API_KEY}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      email: lead.email,
      name: lead.name,
      socialProfiles: [
        { type: 'github', url: lead.profile_url },
      ],
      organization: lead.company,
      customAttributes: {
        github_signal_type: lead.signal.type,
        github_signal_keyword: lead.signal.keyword,
        github_signal_context: lead.signal.context?.slice(0, 500),
        github_signal_repo: lead.signal.repo,
        github_signal_date: lead.signal.captured_at,
        gitleads_top_languages: lead.top_languages?.join(', '),
      },
    }),
  });

  return new Response(response.ok ? 'ok' : 'error', {
    status: response.ok ? 200 : 500,
  });
}

Use Cases for the Combined Dataset

• Identify community members who are actively evaluating competitors — prioritize them for outreach or DevRel conversations
• Find stargazers of competitor repos who are also members of your Slack or Discord — they are already warm community contacts
• Track how often a developer shows GitHub intent signals over time — a member who fires three signals in 30 days is a hot lead
• Segment your Common Room member base by technical stack (top languages from GitLeads) for targeted campaigns
• Alert your DevRel team when a high-follower GitHub user mentions your category in a GitHub issue
• Build segments in Common Room based on GitHub signal type for personalized community nurture flows

Setting Up the GitLeads to Common Room Integration

1. In GitLeads, go to Integrations and copy your webhook URL (or use the n8n/Zapier connector)
2. In Common Room, generate an API key from Settings then Integrations then API
3. Deploy a webhook handler that maps GitLeads payload fields to Common Room member attributes
4. Use lead.profile_url (GitHub URL) as the primary identifier for member matching — Common Room deduplicates on social profiles
5. Add a custom segment in Common Room: "has github_signal_date in last 30 days" to create a live GitLeads signal queue
6. Configure Common Room alerts or Slack notifications for high-priority signal types (competitor mentions, direct keyword hits)

Combining with Other GitLeads Destinations

Common Room works best as the intelligence layer, not the outreach tool. Route the same GitLeads signals to your outreach stack (Smartlead, Instantly, Lemlist) for sequencing, while Common Room gives your DevRel and community team the full-picture view. GitLeads can push the same lead to multiple destinations simultaneously — Common Room for community context, HubSpot for CRM, and Slack for immediate high-intent alerts.