Getting Started

Quickstart Guide

Get GitHub developer leads flowing into your sales tools in under 30 minutes. No scraping, no code required.

Before you start

✓A GitHub account (free) — needed for OAuth connection
✓At least one public repository to track (your own or a competitor's)
✓An account in at least one destination tool (HubSpot, Slack, Smartlead, etc.) — or a webhook URL

Create your GitLeads account

Sign up at gitleads.app with your GitHub account (OAuth) or email. No credit card required for the Free tier — you get 50 leads per month immediately.

Connect your GitHub account

GitLeads requests read-only GitHub OAuth access. This lets it monitor public repository activity (stars, issues, PRs) on your behalf. We never request write access and cannot push to your repositories.

Add a tracked repository

Go to Dashboard → Tracked Repos → Add Repo. Enter any public GitHub repository URL. You can track your own repos (to capture stargazers) or competitor repos (to capture developer intent signals). Start with 1–3 repos.

Add keyword monitors (optional)

Go to Dashboard → Tracked Keywords → Add Keyword. Enter a keyword or phrase. GitLeads scans new GitHub Issues, Pull Requests, Discussions, and commits for matches. Good starting keywords: your product name, a competitor name, or a problem description like "looking for a way to track stargazers".

Connect an integration destination

Go to Dashboard → Integrations. Connect at least one destination — HubSpot, Slack, Smartlead, Instantly, or a webhook URL. This is where your leads will be delivered. Each integration takes 1–3 minutes to configure.

Watch leads come in

GitLeads monitors your tracked repos and keywords continuously. When a new stargazer or keyword match is detected, the lead is enriched with GitHub profile data (name, email if public, bio, company, location, languages) and pushed to your connected destination. Most new customers see their first lead within hours.

What data does each lead include?

GitLeads enriches every captured lead from their public GitHub profile. Here is what is included in every lead record:

{
  "id": "lead_abc123",
  "signal_type": "stargazer",          // or "keyword_issue", "keyword_pr", "keyword_code"
  "signal_source": "acme-corp/rival-sdk",
  "signal_context": "Starred on 2026-04-24",
  "github_username": "jdoe",
  "github_profile_url": "https://github.com/jdoe",
  "name": "Jane Doe",
  "email": "jane@example.com",         // only if publicly listed on GitHub profile
  "bio": "Staff engineer @ Vercel. Loves Rust and distributed systems.",
  "company": "Vercel",
  "location": "San Francisco, CA",
  "followers": 1842,
  "public_repos": 47,
  "account_created_at": "2019-03-12",
  "top_languages": ["TypeScript", "Rust", "Go"],
  "captured_at": "2026-04-24T10:31:00Z"
}

Next steps

HubSpot Integration →

Sync leads to HubSpot contacts with one OAuth click.

Zapier Integration →

Connect any tool via Zapier triggers.

Webhook Reference →

Receive real-time lead payloads to any endpoint.

API Reference →

Pull leads and manage tracking programmatically.

Need help?

Email support@gitleads.app or check the FAQ.