Push GitHub Leads to Customer.io

Customer.io is a behavioral messaging platform widely used by developer-first SaaS companies for onboarding sequences, activation campaigns, and lifecycle emails. When you combine Customer.io with GitHub intent signals from GitLeads, you get a developer lead pipeline that automatically creates or updates people in Customer.io the moment they show buying intent on GitHub.

Why Customer.io for Developer Lead Sequences

Customer.io excels at behavioral triggers and conditional branching — exactly what developer outreach requires. You can send different messages based on which repo a developer starred, which keyword triggered the lead, their primary programming language, or their follower count. Generic email blasts do not work for developers. Customer.io's logic engine lets you get specific.

GitLeads → Customer.io: Two Integration Paths

Option 1: Webhook to Customer.io Track API

GitLeads can POST a webhook payload to any endpoint. Customer.io exposes a Track API that accepts person creation and event tracking. Set GitLeads to POST to your Customer.io Track API endpoint and map the enriched lead fields to Customer.io attributes.

// Webhook handler: GitLeads → Customer.io Track API
import { CustomerIO } from 'customerio-node';

const cio = new CustomerIO(
  process.env.CIO_SITE_ID!,
  process.env.CIO_API_KEY!
);

export async function POST(req: Request) {
  const lead = await req.json(); // GitLeads webhook payload

  // Identify the person in Customer.io
  await cio.identify(lead.github_username, {
    email: lead.email,
    name: lead.name,
    github_username: lead.github_username,
    company: lead.company,
    location: lead.location,
    followers: lead.followers,
    top_languages: lead.top_languages?.join(', '),
    github_bio: lead.bio,
    signal_type: lead.signal_type, // 'stargazer' | 'keyword'
    signal_repo: lead.repo,
    signal_keyword: lead.keyword,
    created_at: Math.floor(Date.now() / 1000),
  });

  // Track the signal event to trigger a campaign
  await cio.track(lead.github_username, {
    name: 'github_signal_captured',
    data: {
      signal_type: lead.signal_type,
      repo: lead.repo,
      keyword: lead.keyword,
    },
  });

  return Response.json({ ok: true });
}

Option 2: Via Zapier or n8n

If you prefer no-code, route GitLeads webhooks through Zapier or n8n. Both have native Customer.io integrations. The workflow: GitLeads webhook trigger → transform payload → Customer.io "Create or Update Person" step → Customer.io "Track Event" step. This lets you add filtering logic (only send leads with emails, only send leads from specific repos) without writing server code.

Customer.io Campaign Setup for GitHub Leads

Once leads are in Customer.io, create a broadcast campaign triggered by the "github_signal_captured" event. Use the signal attributes for personalization:

• Subject: "You starred {{signal_repo}} — here's how [Your Product] fits in"
• Body: reference the specific GitHub signal to establish relevance immediately
• Branch on signal_type: different copy for stargazers vs keyword mentions
• Branch on top_languages: highlight language-specific SDK or integration if available
• Add a 3-day delay before follow-up for non-openers

Customer.io Data Attributes from GitLeads

GitLeads enriches each lead with name, email, GitHub username, profile URL, bio, company, location, follower count, top languages, and the full signal context (which repo was starred, which keyword was matched, signal timestamp). All of these map cleanly to Customer.io person attributes and are available as personalization tokens in your email templates.