Push GitHub Leads to DevRev

Why Send GitHub Signals to DevRev

DevRev is purpose-built for developer tool companies — it combines customer support, product management, and CRM in a single platform designed for dev-tool GTM. If you sell to developers, your ICP already lives on GitHub. GitLeads captures buying signals from GitHub (new repo stars, keyword mentions in issues/PRs/discussions) and DevRev is where those signals should land — tied to Rev Orgs, Rev Users, and your existing support and product data.

Unlike generic CRMs where a GitHub developer is just a tag in a contact field, DevRev connects GitLeads signals to the full customer journey: PLG signup, support tickets, product usage, and now pre-signup GitHub intent. That complete picture makes your sales motion dramatically more effective.

What GitLeads Captures Before Sending to DevRev

• Stargazer signals — developers who starred repos you track (yours, competitors, ecosystem repos)
• Keyword signals — developers who mentioned your tracked keywords in GitHub Issues, PRs, or Discussions
• Lead profile — name, public email, GitHub username, company, bio, location, top programming languages
• Signal context — which repo was starred, or the exact issue/PR URL containing the keyword match
• Signal timestamp — when the signal occurred, so DevRev timelines reflect accurate intent dates

Option 1: Webhook → DevRev API

GitLeads supports outbound webhooks. Configure a webhook in your GitLeads dashboard, then write a small receiver that calls the DevRev API to create or update Rev Users and Rev Orgs.

// Upsert DevRev Rev User from GitLeads webhook payload
import express from "express";
import axios from "axios";

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

const DEVREV_API = "https://api.devrev.ai";
const DEVREV_TOKEN = process.env.DEVREV_TOKEN!;

app.post("/gitleads-webhook", async (req, res) => {
  const lead = req.body;

  await axios.post(
    `${DEVREV_API}/rev-users.create`,
    {
      display_name: lead.name,
      email: lead.email,
      external_ref: `github:${lead.github_username}`,
      custom_fields: {
        github_username: lead.github_username,
        github_company: lead.company,
        gitleads_signal: lead.signal.type,
        gitleads_signal_repo: lead.signal.repo,
        gitleads_signal_url: lead.signal.url,
        gitleads_top_languages: lead.top_languages.join(", "),
      },
    },
    { headers: { Authorization: `Bearer ${DEVREV_TOKEN}` } }
  );

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

app.listen(3000);

Option 2: Zapier → DevRev

GitLeads has a native Zapier integration. Use the Zapier DevRev app to create a Zap that fires on new GitLeads leads and creates DevRev Rev Users without writing code:

1. In GitLeads dashboard → Integrations → Zapier → copy your Zapier trigger URL
2. Create a new Zap in Zapier with "GitLeads: New Lead" as the trigger
3. Add "DevRev: Create Rev User" as the action
4. Map GitLeads fields: name → Display Name, email → Email, github_username → External Ref
5. Map signal context to a custom field so sales reps see what triggered the lead
6. Test and activate — leads appear in DevRev within 60 seconds of GitHub activity

Segmenting DevRev Rev Orgs by GitHub Signal Type

Use DevRev custom fields to segment leads by signal type:

• signal_type = "stargazer" + repo = "your-org/your-repo" → warm leads who starred your own repo
• signal_type = "stargazer" + repo = "competitor/repo" → competitive intercept leads
• signal_type = "keyword" + keyword = "your-product-name" → developers mentioning you in issues/PRs
• signal_type = "keyword" + keyword = "alternative to X" → developers actively evaluating your category

What GitLeads Does Not Do

GitLeads finds the leads and pushes them to DevRev. GitLeads does not send emails, run sequences, or contact developers on your behalf. Your DevRev workflows, Rev Motion plays, and sales team handle outreach. GitLeads is the signal source — DevRev is where you act on those signals.