Push GitHub Developer Leads to Freshservice

Why Route GitHub Signals to Freshservice

Freshservice is primarily an ITSM and service desk platform, but many developer tool companies and DevOps SaaS companies use it for customer success, support ticket routing, and contact management alongside its CRM capabilities. If your team is already working in Freshservice, routing GitHub developer leads there means your signals land where your team already operates — no context switching required.

GitLeads captures two types of GitHub developer signals and can push either into Freshservice via webhook: stargazer signals (new stars on repos you track) and keyword signals (mentions of your brand or product category in Issues, PRs, and Discussions).

Architecture: GitLeads → Freshservice

Freshservice exposes a REST API for creating and updating contacts and tickets. The integration path from GitLeads uses a webhook or automation middleware:

1. GitLeads detects a GitHub signal (new star or keyword match)
2. Enriched lead data is sent to a webhook endpoint (GitLeads native webhook or via Zapier/Make/n8n)
3. The middleware calls the Freshservice Contacts API to create or upsert the contact
4. Optionally: create a Freshservice ticket tagged "github-lead" for follow-up assignment
5. Requester and custom fields populated from GitLeads data

Freshservice Contact Mapping

GitLeads provides the following enriched fields that map cleanly to Freshservice contact properties:

• name → Contact name
• email → Contact email (used for deduplication)
• company → Company name
• bio → Description or custom field
• location → Contact location
• github_url → Custom field "GitHub Profile"
• signal_type → Custom field "Lead Source" (stargazer or keyword)
• signal_context → Custom field "Signal Detail" (which repo, which keyword)
• top_languages → Custom field "Tech Stack"

Webhook Implementation with n8n

Here is an n8n workflow pattern for routing GitLeads signals to Freshservice:

// n8n HTTP Request node — create/upsert Freshservice contact
// Triggered by GitLeads webhook
const lead = $input.first().json;

const contactPayload = {
  name: lead.name || lead.github_username,
  email: lead.email,
  description: `GitHub signal: ${lead.signal_type}\nContext: ${lead.signal_context}\nBio: ${lead.bio}`,
  company_name: lead.company,
  address: lead.location,
  custom_fields: {
    github_profile: lead.github_url,
    signal_type: lead.signal_type,
    tech_stack: (lead.top_languages || []).join(', '),
    followers: lead.followers,
  },
  tags: [`github-lead`, `gitleads-${lead.signal_type}`],
};

// POST to Freshservice Contacts API
// https://{your-domain}.freshservice.com/api/v2/contacts
return {
  method: 'POST',
  url: `https://${$env.FS_DOMAIN}.freshservice.com/api/v2/contacts`,
  headers: {
    Authorization: `Basic ${Buffer.from($env.FS_API_KEY + ':X').toString('base64')}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ contact: contactPayload }),
};

Creating Freshservice Tickets for High-Intent Leads

For high-priority signals — such as a developer at a Fortune 500 company starring your repo — you can automatically create a Freshservice ticket for your sales or DevRel team to action:

// Create a Freshservice ticket for high-follower leads
const lead = $input.first().json;

if ((lead.followers || 0) >= 500 || lead.company) {
  const ticketPayload = {
    subject: `GitHub lead: ${lead.name || lead.github_username} @ ${lead.company || 'unknown'}`,
    description: `<b>Signal:</b> ${lead.signal_type}<br>
<b>Context:</b> ${lead.signal_context}<br>
<b>GitHub:</b> <a href="${lead.github_url}">${lead.github_url}</a><br>
<b>Bio:</b> ${lead.bio}<br>
<b>Languages:</b> ${(lead.top_languages || []).join(', ')}`,
    source: 2, // Email
    status: 2, // Open
    priority: lead.followers >= 1000 ? 3 : 2, // High or Medium
    tags: ['github-lead', 'gitleads'],
  };
  // POST to /api/v2/tickets
}

Using Zapier Instead

If you prefer no-code, GitLeads supports Zapier as an integration destination. Set up a Zap:

1. Trigger: GitLeads New Lead (via Zapier webhook)
2. Action: Freshservice — Create Contact
3. Optional Action: Freshservice — Create Ticket
4. Map GitLeads fields to Freshservice fields in the Zapier UI
5. Add a Filter step to only create tickets for leads with email present