Push GitHub Leads to Dealfront (Leadfeeder)

GitLeads + Dealfront: GitHub Intent Meets Website Intelligence

Dealfront (formerly Leadfeeder) identifies companies visiting your website and enriches them with firmographic data. GitLeads identifies individual developers showing buying intent on GitHub — starring your repos, mentioning your keywords in issues and PRs.

Combining both: you see which companies are researching you (Dealfront) AND which individual developers within those companies are actively evaluating tools on GitHub (GitLeads). That is the full developer GTM picture.

What GitLeads Captures That Dealfront Cannot

• Individual developer identity — name, GitHub username, email, bio
• Signal context — exactly what repo they starred or what they said in an issue
• GitHub-native intent — signals from activity that website trackers cannot see
• Open source community signals — contributors, issue commenters, fork authors
• Real-time notification — signals pushed within minutes of the GitHub event

Integration Options: GitHub Leads to Dealfront

The recommended integration pattern uses an intermediate CRM since Dealfront does not offer a direct inbound contact push API:

Option 1: Via HubSpot (Recommended)

GitLeads pushes GitHub leads to HubSpot as contacts. Dealfront syncs with HubSpot bidirectionally. New developer contacts created by GitLeads become visible in Dealfront with company-level matching.

// GitLeads webhook payload -> HubSpot contact -> Dealfront sync
const contact = {
  email: lead.email,
  firstname: lead.firstName,
  lastname: lead.lastName,
  company: lead.company,
  github_username: lead.githubUsername,   // custom HubSpot property
  github_signal: lead.signalContext,      // custom HubSpot property
  github_signal_type: lead.signalType,    // 'stargazer' | 'keyword'
};

await hubspotClient.crm.contacts.basicApi.create({ properties: contact });
// Dealfront <-> HubSpot sync picks up the new contact automatically

Option 2: Via Salesforce

If your team uses Salesforce as the primary CRM, GitLeads can push developer leads there directly. Dealfront natively syncs with Salesforce, so new Lead records created by GitLeads appear in Dealfront's account-matching view.

Option 3: Via Webhook and Custom Script

// Route GitLeads webhook to Dealfront Leads API
import Fastify from 'fastify';

const app = Fastify();

app.post('/gitleads-webhook', async (req, reply) => {
  const lead = req.body as GitLeadsPayload;

  const dfContact = {
    email: lead.email,
    name: `${lead.firstName} ${lead.lastName}`,
    company_name: lead.company,
    custom_fields: {
      github_signal: lead.signalContext,
      github_username: lead.githubUsername,
    },
  };

  await fetch('https://api.dealfront.com/v1/contacts', {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${process.env.DEALFRONT_API_KEY}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify(dfContact),
  });

  return reply.send({ ok: true });
});

Setting Up GitLeads for Dealfront Workflows

1. Sign up at gitleads.app and add repos or keywords to track
2. Choose your integration: HubSpot, Salesforce, or webhook
3. Configure the Dealfront sync in Dealfront settings (HubSpot or Salesforce)
4. Set up a Dealfront feed filter to highlight contacts with "github_signal" custom field populated
5. Alert your sales team when a GitHub lead matches a company already in Dealfront

High-Intent Keywords to Prioritize

Use GitLeads keyword specificity to pre-qualify leads before pushing to Dealfront:

• "pricing" or "enterprise" in GitHub issue text — explicit buying interest
• "alternative to [your product]" — competitive evaluation signal
• "self-hosted" or "on-premise" — enterprise deal indicator
• Stars on your competitor's repo — switching intent
• Stars on your own repo within hours of a website visit (cross-signal)