Push GitHub Leads to Vitally: Developer-Led CS Signal Routing

Why Vitally for Developer-Led Customer Success

Vitally is a CS platform built for SaaS teams that need a real-time view of account health, user engagement, and product usage signals. For companies with a developer audience — API tools, dev infrastructure, security platforms, data tools — Vitally is often the CS layer sitting above Salesforce or HubSpot. The problem: Vitally is fed by product analytics and CRM data, but it has no native GitHub signal. A prospect who stars your repo, mentions your product name in a GitHub Issue, or contributes to a related open-source project is showing real intent — but that signal never makes it into Vitally without GitLeads.

The GitHub Signal Types That Matter for Vitally

• New stargazers on your product repo — developers evaluating your tool for active use
• New stargazers on competitor repos — prospects in evaluation mode, comparing alternatives
• Keyword mentions of your product name in GitHub Issues — existing users discussing your product publicly
• Keyword mentions of your product name in PRs — developers integrating your tool into real codebases
• Keyword mentions in commit messages — production usage signals with strong commercial intent
• Stars on related ecosystem repos — category-level intent signals from your target ICP

What GitLeads Captures and Routes to Vitally

• GitHub username, display name, and public email (if set)
• Company name from GitHub bio or organization membership
• Profile URL, follower count, and account age
• Top programming languages — indicates tech stack fit
• Signal context: which repo was starred, which keyword matched, and the surrounding text
• Signal timestamp — so Vitally playbooks can trigger based on recency

Setting Up GitLeads → Vitally Integration

1. Sign up at gitleads.app and configure your stargazer or keyword signals
2. In GitLeads, navigate to Integrations → Webhook
3. Copy your Vitally Organization API Key from Vitally Settings → API
4. Create a webhook destination in GitLeads pointing to your Vitally ingestion endpoint
5. Map GitLeads fields: github_username → userId, company → accountId, signal_context → trait
6. Enable the integration and confirm test payloads appear in Vitally as user traits
7. Build a Vitally Playbook triggered by the new trait (e.g., github_signal_type = stargazer)

// Push a GitLeads GitHub signal to Vitally via their REST API
// GitLeads webhook handler (Next.js API route)
import type { NextRequest } from 'next/server';

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

  const VITALLY_ORG_ID = process.env.VITALLY_ORG_ID!;
  const VITALLY_API_KEY = process.env.VITALLY_API_KEY!;

  // Upsert user in Vitally with GitHub signal traits
  await fetch(`https://rest.vitally.io/resources/users`, {
    method: 'POST',
    headers: {
      'Authorization': `Basic ${Buffer.from(VITALLY_API_KEY + ':').toString('base64')}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      externalId: lead.github_username,
      name: lead.name ?? lead.github_username,
      email: lead.email,
      organizationExternalId: lead.company ?? 'unknown',
      traits: {
        github_signal_type: lead.signal_type,
        github_signal_repo: lead.repo,
        github_signal_keyword: lead.keyword ?? null,
        github_bio: lead.bio,
        github_followers: lead.followers,
        github_top_languages: lead.top_languages?.join(', '),
        github_profile_url: lead.profile_url,
        github_signal_detected_at: lead.enriched_at,
      },
    }),
  });

  return Response.json({ ok: true });
}

Vitally Playbooks to Build from GitHub Signals

• New Prospect Playbook — triggered when github_signal_type = "stargazer" and no existing account in Vitally; assign a CS rep and send a welcome email sequence
• Competitor Evaluation Playbook — triggered when github_signal_repo matches a competitor repo slug; escalate to AE for competitive outreach
• Free-to-Paid Nudge — triggered when an existing free-tier user appears as a stargazer on a paid-feature-related repo
• At-Risk Account Playbook — triggered when an existing customer stars a direct competitor repo; flag for CS intervention
• DevRel Engagement Playbook — triggered when github_signal_type = "keyword_mention" in a public repo; route to DevRel for community engagement

Who Benefits from GitHub → Vitally Routing

• CS teams at API-first companies — know when free users are actively evaluating your product on GitHub
• DevRel teams — surface community members who mention your product before they open a support ticket
• Expansion teams — identify accounts already using your product who are also evaluating add-ons or competitors
• Sales teams — get warm lead alerts when prospects star your repo while in an active sales conversation