Push GitHub Leads to Ortto for Developer Journey Automation

Why Ortto for Developer-Led Growth

Ortto (formerly Autopilot) combines CRM, journey automation, and analytics in one platform. For developer-focused GTM teams, Ortto's journey builder maps directly onto the GitHub signal lifecycle: a stargazer enters a nurture track, a keyword mention triggers a high-priority sequence, and a competitor evaluator gets fast-tracked to sales. The key is piping the right signals in at the right time.

GitLeads captures developer buying signals from GitHub — new stargazers on tracked repos, keyword mentions in issues and PRs — and pushes enriched lead profiles wherever your stack lives. Ortto is a natural destination: it receives the lead, enriches the person record, and kicks off the appropriate journey automatically.

Integration Architecture: GitLeads → Ortto

The cleanest path uses GitLeads webhooks into Ortto via their REST API or through n8n/Make as middleware:

// n8n webhook node receiving GitLeads signal
// then creating/updating Ortto person via REST API

const orttoApiKey = process.env.ORTTO_API_KEY;
const orttoBase = 'https://api.ap3api.com/v1';

interface GitLeadsSignal {
  github_username: string;
  email?: string;
  name?: string;
  company?: string;
  signal_type: 'stargazer' | 'keyword';
  signal_context: string;
  repo?: string;
  keyword?: string;
}

async function pushToOrtto(signal: GitLeadsSignal) {
  const person = {
    fields: {
      'str::email': signal.email ?? `${signal.github_username}@github.noreply`,
      'str::first': signal.name?.split(' ')[0] ?? signal.github_username,
      'str::last': signal.name?.split(' ').slice(1).join(' ') ?? '',
      'str::company': signal.company ?? '',
      // Custom fields in Ortto
      'str::cm4abc123--github-username': signal.github_username,
      'str::cm4abc124--signal-type': signal.signal_type,
      'str::cm4abc125--signal-context': signal.signal_context,
      'str::cm4abc126--source-repo': signal.repo ?? '',
    },
    tags: [
      'github-signal',
      signal.signal_type === 'stargazer' ? 'stargazer' : 'keyword-mention',
    ],
  };

  const response = await fetch(`${orttoBase}/person/merge`, {
    method: 'POST',
    headers: {
      'X-Api-Key': orttoApiKey,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({ people: [person] }),
  });

  if (!response.ok) {
    throw new Error(`Ortto API error: ${response.status}`);
  }

  return response.json();
}

Setting Up Custom Fields in Ortto

Before pushing leads, create these custom fields in Ortto under People → Custom Fields:

• GitHub Username (Text) — links back to the developer's profile for personalization
• Signal Type (Text) — "stargazer" or "keyword" to drive journey branching
• Signal Context (Long Text) — the exact repo starred or keyword phrase matched
• Source Repo (Text) — the tracked repository that triggered the signal
• GitHub Followers (Number) — for influencer scoring and DevRel routing
• Top Languages (Text) — primary programming language for content relevance

Building Ortto Journeys for GitHub Signals

Ortto's journey builder lets you create branching automation based on person attributes and tags. Map your GitLeads signals to specific journey entry points:

• Journey 1 — Stargazer Nurture: Entry trigger "tag added: stargazer" → 3-touch educational email sequence over 14 days → branch if opened → upgrade to demo invite
• Journey 2 — Keyword High Intent: Entry trigger "tag added: keyword-mention" → immediate Slack notification to SDR → 48-hour wait → personalized technical email with signal context
• Journey 3 — Competitor Evaluation: Entry filter "signal_context contains [competitor name]" → immediate sales alert + fast-track sequence → skip nurture entirely
• Journey 4 — DevRel Influencers: Entry filter "github_followers > 500" → personal DevRel outreach email, not sales sequence

Using Ortto Smart Segments for GitHub Lead Scoring

Ortto's Smart Segments auto-update as lead attributes change. Create segments that mirror your GitLeads signal quality tiers:

// Ortto Smart Segment logic

Segment: "Hot GitHub Leads"
  signal_type = "keyword"
  AND created_at > 7 days ago
  AND email IS NOT NULL

Segment: "Stargazer Nurture Pool"
  tag = "stargazer"
  AND signal_type = "stargazer"
  AND NOT IN any journey

Segment: "Competitor Evaluators"
  signal_context CONTAINS "vs " OR "alternative" OR "migration"
  AND signal_type IN ["stargazer", "keyword"]

Segment: "DevRel Targets"
  github_followers > 500
  AND top_languages CONTAINS "TypeScript" OR "Go" OR "Rust"

Zapier Alternative: Direct Ortto API via GitLeads Webhook

If you prefer no middleware, configure a GitLeads webhook to hit your own endpoint that calls the Ortto API directly. GitLeads sends a POST with the full lead payload including signal context, GitHub profile data, and enrichment fields. Your endpoint calls `POST /v1/person/merge` with the mapped fields and triggers the appropriate journey via tag assignment.