Push GitHub Leads to Amplemarket

Why Amplemarket + GitHub Signals Work Together

Amplemarket is an AI-driven sales engagement platform designed to automate outbound sequences across email, LinkedIn, and phone. GitLeads is the signal layer upstream of that: it captures developers who star your tracked GitHub repos or mention your keywords in issues, PRs, and discussions, then enriches those profiles with name, email, company, GitHub bio, top languages, and follower count. Together, they let you build a developer-intent pipeline that triggers Amplemarket sequences on real buying signals rather than stale list imports.

What GitLeads Sends to Amplemarket

• Full name (from GitHub profile)
• Email address (when publicly listed)
• GitHub username and profile URL
• Company name and location from bio
• Top programming languages
• Follower count and public repo count
• Signal context: which repo they starred, which keyword triggered, exact issue/PR text
• Timestamp of the signal event

Integration Architecture: GitLeads → Webhook → Amplemarket

Amplemarket does not offer a direct inbound webhook endpoint for lead creation, so the standard pattern is a middleware layer: GitLeads fires a webhook, a lightweight automation (n8n, Make, Zapier, or a custom function) receives it, transforms the payload, and calls the Amplemarket API to create a contact and enroll them in a sequence.

// n8n HTTP Request node — Amplemarket contact create
const gitLeadsPayload = $input.item.json;

const ampleResponse = await $http.post(
  'https://api.amplemarket.com/contacts',
  {
    email: gitLeadsPayload.email,
    first_name: gitLeadsPayload.name?.split(' ')[0] ?? '',
    last_name: gitLeadsPayload.name?.split(' ').slice(1).join(' ') ?? '',
    company: gitLeadsPayload.company ?? '',
    linkedin_url: gitLeadsPayload.linkedinUrl ?? '',
    custom_fields: {
      github_username: gitLeadsPayload.githubUsername,
      signal_type: gitLeadsPayload.signalType,
      signal_repo: gitLeadsPayload.repoFullName ?? '',
      signal_keyword: gitLeadsPayload.keyword ?? '',
      github_followers: gitLeadsPayload.followers,
      top_languages: (gitLeadsPayload.topLanguages ?? []).join(', '),
    },
  },
  {
    headers: {
      Authorization: `Bearer ${process.env.AMPLEMARKET_API_KEY}`,
      'Content-Type': 'application/json',
    },
  }
);

// Enroll in developer-targeted sequence
if (gitLeadsPayload.email && ampleResponse.data?.id) {
  await $http.post(
    `https://api.amplemarket.com/contacts/${ampleResponse.data.id}/enroll`,
    { sequence_id: process.env.AMPLEMARKET_DEV_SEQUENCE_ID },
    { headers: { Authorization: `Bearer ${process.env.AMPLEMARKET_API_KEY}` } }
  );
}

Sequence Personalization with GitHub Signal Context

The highest-converting pattern is a first email that references the specific GitHub signal. Map signal context to sequence variables in Amplemarket:

• Stargazer signal → "Saw you starred {{signal_repo}} — wanted to share how teams like yours use {{product}}"
• Keyword signal → "Noticed you mentioned {{signal_keyword}} in a GitHub issue — here's how we solve exactly that"
• High-follower engineer → personalize with follower count threshold for DevRel vs. AE routing
• Top language match → route Python devs to Python SDK sequence, Go devs to Go SDK sequence

Routing Rules: Which Leads Go to Amplemarket vs. Other Tools

• Has public email + company domain → Amplemarket sequence (highest deliverability)
• No email but has LinkedIn URL → Amplemarket LinkedIn step only
• Has email only (no company) → enrichment step in Clay first, then Amplemarket
• High-follower DevRel target → Slack alert instead of automated sequence
• Enterprise domain (Fortune 500) → Salesforce account match first before Amplemarket