Push GitHub Leads to Cognism: Enrich Developer Intent Signals with B2B Intelligence

Why Combine GitLeads and Cognism?

GitLeads finds developers showing buying signals on GitHub — new stars on your tracked repos, keyword mentions in issues and PRs, commit message patterns. Cognism provides phone-verified mobile numbers, GDPR-compliant B2B data, and Bombora intent signals. Together, they give your sales team the richest possible view of a developer prospect: what they are building on GitHub plus verified contact information.

GitLeads does not send emails or make calls. It finds the signals. Cognism provides the contact enrichment. Your existing outreach stack (Cognism Prospector, Salesforce, HubSpot, or cold email tools) handles the actual outreach.

Integration Architecture

The GitLeads → Cognism integration flow works via webhook or Zapier/n8n:

1. GitLeads captures a developer signal (e.g., new star on your GitHub repo)
2. GitLeads enriches the lead with GitHub profile data: username, email, bio, company, location, languages
3. GitLeads pushes the enriched lead to a webhook endpoint you control
4. Your middleware (n8n, Zapier, or custom code) calls the Cognism Enrich API with the developer's email or LinkedIn URL
5. Cognism returns phone-verified mobile, work email, company firmographics, and Bombora intent topics
6. The fully enriched record is pushed to your CRM (Salesforce, HubSpot) or sequencing tool

GitLeads Webhook Configuration

In your GitLeads dashboard, navigate to Integrations → Webhook and configure:

{
  "url": "https://your-n8n-instance.com/webhook/github-to-cognism",
  "events": ["stargazer.new", "keyword.match"],
  "headers": {
    "Authorization": "Bearer YOUR_WEBHOOK_SECRET"
  }
}

Cognism Enrich API Call

Once GitLeads pushes the lead, call Cognism's Enrichment API to get verified contact data:

async function enrichWithCognism(githubLead: GitLeadsLead) {
  const response = await fetch('https://api.cognism.com/v1/enrich', {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${process.env.COGNISM_API_KEY}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      email: githubLead.email,
      linkedin_url: githubLead.linkedinUrl, // if available from GitHub bio
      company_name: githubLead.company,
    }),
  });

  const cognismData = await response.json();

  return {
    // From GitLeads
    githubUsername: githubLead.username,
    signalType: githubLead.signalType,
    signalContext: githubLead.signalContext,
    repoStarred: githubLead.repoName,
    topLanguages: githubLead.topLanguages,

    // From Cognism enrichment
    mobilePhone: cognismData.mobile_phone,
    workEmail: cognismData.work_email,
    jobTitle: cognismData.job_title,
    companySize: cognismData.company_employees,
    companyRevenue: cognismData.company_revenue,
    intentTopics: cognismData.bombora_intent_topics,
    gdprCompliant: cognismData.do_not_call_status,
  };
}

n8n Workflow for GitLeads → Cognism → CRM

A typical n8n workflow for this integration:

1. Webhook node: receives GitLeads signal payload
2. IF node: filter by signal type (stargazer) or keyword (e.g., "pricing", "enterprise")
3. HTTP Request node: POST to Cognism /v1/enrich with email from GitLeads payload
4. Merge node: combine GitLeads + Cognism response into unified lead record
5. HubSpot/Salesforce node: create or update contact with enriched data
6. Slack node: notify your sales team for high-priority signals (>500 GitHub followers, known company)

High-Value Signal Patterns for Cognism Enrichment

• Developers who star a competitor's repo — enrich immediately and add to competitor displacement sequence
• Keywords like "pricing", "enterprise plan", or "support SLA" in GitHub issues — high-intent buyer signal
• Developers at companies with >200 employees (visible in GitHub bio) — Cognism provides verified mobile for SDR calling
• Contributors to your tracked repos who mention a specific use case — personalized outreach opportunity
• Developers with Bombora intent topics matching your product category — double intent signal

GDPR and Compliance Considerations

Cognism's data is GDPR and CCPA compliant. Their Diamond Data includes do-not-call verification. Always check `do_not_call_status` before passing leads to phone outreach sequences. GitLeads only captures publicly available GitHub profile data — email addresses are only captured when developers have made them public in their GitHub profile.