Documentation
Frequently Asked Questions
Common questions about GitLeads — what it does, how it works, and how to get the most out of it.
Product
What exactly does GitLeads do?
GitLeads monitors public GitHub activity — repository stars, keyword mentions in Issues, Pull Requests, Discussions, and code — and turns those signals into enriched developer lead records. Each lead includes name, email (if public), GitHub username, bio, company, location, follower count, and top programming languages. Leads are pushed in real time to the sales and marketing tools you already use.
Does GitLeads send emails on my behalf?
No. GitLeads finds leads and pushes them to your tools. We do not send emails, create outreach sequences, or contact anyone directly. Your existing email tool (Smartlead, Instantly, Apollo, etc.) handles outreach.
What is a "signal"?
A signal is a public GitHub action that indicates developer interest or buying intent. GitLeads captures two types: (1) Stargazer signals — a developer stars a tracked repository. (2) Keyword signals — a developer mentions a tracked keyword in a GitHub Issue, PR, Discussion, or code commit.
Which repositories can I track?
Any public GitHub repository. Most customers track their own product repos (to capture people who star their project), competitor repos (to capture developers who are evaluating alternatives), and popular open-source ecosystem repos used by their ICP.
How quickly does GitLeads detect new signals?
Stargazer events are typically captured within 5–15 minutes of the star event. Keyword signals (Issues, PRs, Discussions) are scanned on a rolling basis and typically captured within 30–60 minutes of posting.
Lead Data
What data does each lead include?
Every lead includes: GitHub username, profile URL, display name (if set), public email (if listed on their GitHub profile), bio, company (from profile), location, follower count, public repo count, account creation date, and top programming languages by commit activity.
Why do some leads not have an email address?
GitLeads only captures emails that the developer has publicly listed on their GitHub profile. Many developers do not list an email publicly, or use a different email for GitHub than for business contact. GitLeads does not guess, harvest, or purchase emails — we only surface what the developer has chosen to make public.
Can I export leads to CSV?
Yes. Go to Dashboard → Leads → Export. You can export all leads or filter by date range, signal type, or tracked repo before exporting. CSV export is available on all paid plans.
How long are leads stored?
Lead records are stored for the lifetime of your account. Deleting a tracked repo or keyword does not delete leads already captured from it. You can manually delete individual leads or bulk-delete from the dashboard.
Integrations
Which integrations does GitLeads support?
Native integrations: HubSpot, Slack, Smartlead, Instantly, Lemlist, Apollo, Clay, Pipedrive, Salesforce. Automation layer integrations: Zapier, Make (Integromat), n8n. Generic: Webhooks (any HTTP endpoint), CSV export. We add new integrations regularly — check the Integrations page for the current list.
Can I push leads to multiple destinations at the same time?
Yes. You can connect multiple integrations simultaneously. For example, you can push new leads to both HubSpot (for CRM) and Slack (for real-time alerts) at the same time.
Does GitLeads work with n8n and Make?
Yes, via webhooks. Configure a webhook destination in GitLeads and point it at your n8n or Make webhook URL. The lead payload follows the standard GitLeads webhook format documented in the Webhook Reference.
Plans & Billing
What does the Free plan include?
50 leads per month, up to 3 tracked repositories, up to 3 keyword monitors, and 1 integration destination. Free forever — no credit card required.
What counts as a "lead"?
Each unique GitHub developer captured by GitLeads in a given calendar month counts as one lead. If the same developer triggers multiple signals (e.g. they star your repo and also appear in a keyword match), they are counted as one lead for that month.
What happens if I hit my monthly lead limit?
New signals are paused until the next billing cycle resets your quota. You will receive an email notification when you reach 80% and 100% of your limit. Upgrade at any time to restore signal capture immediately.
Can I cancel at any time?
Yes. Cancel from Dashboard → Settings → Billing. Your plan stays active until the end of the current billing period. No cancellation fees.
Is there an annual discount?
Yes — annual billing is 20% cheaper than monthly for all paid plans. Switch to annual billing in Dashboard → Settings → Billing.
Privacy & Compliance
Is GitLeads GDPR compliant?
GitLeads only captures data that developers have chosen to make publicly available on their GitHub profiles. Using publicly available contact information for legitimate business outreach is generally permissible under GDPR's legitimate interests basis. GitLeads processes data under a Data Processing Agreement (DPA) available on request. We do not store any data beyond what is necessary to deliver the service.
Does GitLeads violate GitHub's Terms of Service?
No. GitLeads accesses public GitHub data through GitHub's official REST API and authenticated OAuth connections, within GitHub's documented rate limits. We do not scrape GitHub without authentication or circumvent any access controls.
What GitHub permissions does GitLeads request?
GitLeads requests read-only access to public repository data via GitHub OAuth. We never request write access, access to private repositories, or any permission beyond what is needed to monitor public activity. The exact OAuth scope is read:user and public_repo.
Can I request deletion of my account data?
Yes. Email privacy@gitleads.app to request full deletion of your account and all associated lead data. Deletion is processed within 30 days per GDPR Article 17.
Still have questions?
Email support@gitleads.app — we typically respond within a few hours on business days.