Push GitHub Leads to Yesware

What Is Yesware and Why Connect It to GitHub Signals

Yesware is an email productivity and sales engagement platform that runs inside Gmail and Outlook. It provides email tracking, multi-touch campaigns, meeting scheduling, and reporting — all without requiring a separate sales engagement platform login. Sales teams at developer-tool companies use Yesware to run outreach sequences directly from their inbox.

The challenge: Yesware is powerful for outreach, but it does not generate leads. You need a signal source. GitLeads solves that — it monitors GitHub for developer buying signals (new stargazers on tracked repos, keyword mentions in Issues, PRs, and discussions) and pushes enriched developer profiles to Yesware via webhook so you can trigger sequences the moment intent appears.

How the GitLeads to Yesware Integration Works

GitLeads does not have a native Yesware connector, but the integration is straightforward using webhooks plus Yesware API or a middleware layer like Zapier, Make, or n8n.

Option 1: GitLeads Webhook → n8n/Make → Yesware

// n8n webhook handler: receive GitLeads signal, push to Yesware
// 1. GitLeads fires a POST to your n8n webhook URL
// 2. n8n maps the lead fields to a Yesware contact create call

// GitLeads webhook payload (TypeScript interface)
interface GitLeadsSignal {
  github_username: string;
  name: string | null;
  email: string | null;        // public email if available
  bio: string | null;
  company: string | null;
  location: string | null;
  followers: number;
  top_languages: string[];
  signal_type: 'stargazer' | 'keyword';
  signal_context: string;      // issue/PR text or repo name
  profile_url: string;
}

// Yesware Contact API call (via n8n HTTP node)
const yeswareContact = {
  email: signal.email,
  first_name: signal.name?.split(' ')[0] ?? signal.github_username,
  last_name: signal.name?.split(' ').slice(1).join(' ') ?? '',
  company: signal.company,
  title: signal.bio,
  custom_fields: {
    github_username: signal.github_username,
    signal_context: signal.signal_context,
    top_languages: signal.top_languages.join(', '),
  },
};

Option 2: GitLeads Webhook → Zapier → Yesware

If you prefer Zapier: create a Zap with a "Webhooks by Zapier" trigger (paste the GitLeads webhook URL into your GitLeads integration settings), then use the Yesware action to create a contact or add to a campaign. Zapier has a native Yesware integration that handles OAuth automatically.

Step-by-Step Setup

1. Sign up at gitleads.app and connect your GitHub account
2. Configure signal sources: add repos to track for stargazer signals, or add keywords for issue/PR monitoring
3. In GitLeads → Integrations → Webhook, create a new webhook endpoint
4. In n8n (or Make/Zapier), create a workflow that receives the GitLeads webhook payload
5. Add an HTTP node to call the Yesware Contacts API (POST /api/v1/contacts) with the lead email and metadata
6. Optionally add the contact to a Yesware campaign using POST /api/v1/campaigns/{id}/recipients
7. Test with a sample GitHub event and verify the contact appears in Yesware

Which GitHub Signals Work Best with Yesware

• Keyword mentions in Issues: developer is actively researching or experiencing a problem your product solves
• Stargazers on competitor repos: developer is evaluating alternatives — ideal timing for comparison outreach
• PR descriptions that reference your category keywords: developer is actively building something relevant
• Stars on your own repo: developer liked what they saw — follow up with a personalized Yesware sequence

Lead Data Available for Yesware Personalization

• name + email: required for Yesware contact creation; GitLeads surfaces public GitHub email when available
• company: use for account-based filtering — skip individuals at non-target companies
• top_languages: personalize subject lines — e.g., "noticed you work with Go + Kubernetes"
• signal_context: paste the triggering issue or PR excerpt into the first line of your sequence for 1:1 relevance
• bio: use to determine seniority ("founding engineer", "staff engineer") for routing to enterprise vs. PLG sequences
• followers: proxy for developer influence — high-follower leads may warrant manual outreach instead of automated sequence