Integrations
Zapier Integration
Connect GitLeads to 7,000+ apps through Zapier. When GitLeads captures a new GitHub developer lead, Zapier can automatically add them to any tool in your stack — from Salesforce to Notion to Google Sheets.
How It Works
The GitLeads Zapier integration uses a webhook-based trigger. GitLeads sends a payload to a Zapier Catch Hook URL every time a new lead is captured. You then map the lead fields to any Zapier action.
Trigger: GitLeads New Lead (via Webhooks by Zapier)
Fires when GitLeads detects a new GitHub signal and creates a lead record.
The GitLeads app is currently listed in Zapier as a beta integration. During beta, use Webhooks by Zapier → Catch Hook as the trigger (see setup steps below).
Step-by-Step Setup
Step 1: Create a Zap with Webhooks by Zapier
- Go to zapier.com and create a new Zap
- Select Webhooks by Zapier as the trigger app
- Choose Catch Hook as the trigger event
- Zapier will generate a unique webhook URL — copy it
Step 2: Add the Zapier Webhook URL to GitLeads
- In GitLeads, go to Dashboard → Integrations → Webhooks
- Click Add Webhook
- Paste your Zapier Catch Hook URL
- Click Save
- Click Test Webhook — this sends a sample payload to Zapier
Step 3: Map fields in Zapier
Back in Zapier, after the test webhook fires, you will see all available lead fields. Map them to your action app. Here are the fields available:
data__id → lead_abc123 data__signal_type → stargazer data__signal_source → competitor/their-sdk data__github_username → jdoe data__name → Jane Doe data__email → jane@example.com data__bio → Staff engineer @ Vercel data__company → Vercel data__location → San Francisco, CA data__followers → 1842 data__top_languages → TypeScript, Rust, Go data__captured_at → 2026-04-24T10:31:00Z
Zapier flattens nested JSON using double underscores. The data__ prefix corresponds to the data object in the GitLeads webhook payload.
Step 4: Turn on your Zap
Turn on the Zap. From this point, every new lead captured by GitLeads will trigger the Zap automatically.
Example Zaps
GitLeads → Google Sheets
Append each new lead as a row in a Google Sheets spreadsheet. Useful for teams that review leads manually or want a simple reporting view without a CRM.
Map: data__name, data__email, data__company, data__signal_type, data__signal_source, data__captured_at
GitLeads → Salesforce
Create a Salesforce Lead record for each GitHub signal. Use data__signal_type as the Lead Source field so your sales team knows where each lead came from.
Map: data__name → First Name + Last Name, data__email → Email, data__company → Company, data__signal_type → Lead Source
GitLeads → Slack (custom format)
Send a Slack message with a custom format — for example, including the lead's GitHub bio and follower count, which the native GitLeads Slack integration does not expose.
Message: "New {{data__signal_type}} lead: {{data__name}} ({{data__followers}} followers) — {{data__github_profile_url}}"
GitLeads → Notion database
Add each lead as a Notion database page. Useful for DevRel teams that track developer relationships in Notion rather than a sales CRM.
Map: data__name, data__github_username, data__bio, data__company, data__top_languages
GitLeads → Airtable
Log leads to an Airtable base for enrichment, scoring, or routing decisions that require more flexibility than a standard CRM.
Map all fields — Airtable's flexible columns handle the full lead payload cleanly
Filtering by Signal Type
If you only want your Zap to fire for specific signal types (e.g. only competitor stargazers, not keyword matches), add a Filter by Zapier step between the trigger and action:
Filter step:
Only continue if data__signal_type (Text) Exactly matches stargazer
Available signal type values: stargazer, keyword_issue, keyword_pr, keyword_code
Zapier vs Native Integrations
GitLeads has native (direct) integrations for HubSpot, Slack, Smartlead, Instantly, Lemlist, Apollo, Clay, Pipedrive, and Salesforce. For these tools, the native integration is faster to set up and more reliable than Zapier.
Use Zapier when: the tool you need is not natively supported, you want to combine multiple actions in one flow (e.g. add to Salesforce + notify in Slack + add to Notion), or you need conditional routing logic based on signal type.