Push GitHub Leads to Linear

Developer tool companies often run their sales pipeline inside Linear — the same tool their engineering team uses. It reduces context-switching, keeps technical founders close to GTM activity, and avoids forcing a separate CRM on a team that lives in their IDE and GitHub. GitLeads can push enriched GitHub leads directly to Linear via webhook, giving your team a developer-native prospecting workflow.

Why Dev-Tool Companies Run Sales in Linear

• Engineering-led sales teams prefer Linear's keyboard-driven interface over traditional CRMs
• Technical founders already review Linear daily — adding a 'Leads' team avoids tool sprawl
• Linear's issue metadata (assignee, priority, labels, cycle) maps cleanly to pipeline stages
• No per-seat CRM cost for early-stage startups doing founder-led sales
• Linear API is developer-friendly — webhook integration takes under an hour to build

How the GitLeads → Linear Integration Works

GitLeads does not have a native Linear connector. Use the webhook destination to forward enriched lead payloads to a lightweight relay (a Cloudflare Worker, Vercel Edge Function, or n8n workflow) that calls the Linear GraphQL API to create issues in your GTM team.

// Cloudflare Worker: GitLeads webhook → Linear issue
interface GitLeadsPayload {
  leadName: string;
  githubUsername: string;
  profileUrl: string;
  company?: string;
  bio?: string;
  email?: string;
  followers: number;
  topLanguages: string[];
  signalType: 'stargazer' | 'keyword';
  signalContext: string;
}

export default {
  async fetch(request: Request, env: Env): Promise<Response> {
    const payload: GitLeadsPayload = await request.json();

    const priority = payload.followers > 500 ? 1 : // urgent
                     payload.followers > 100 ? 2 : // high
                     3; // normal

    const description = [
      `**GitHub**: [${payload.githubUsername}](${payload.profileUrl})`,
      payload.company ? `**Company**: ${payload.company}` : '',
      payload.email ? `**Email**: ${payload.email}` : '',
      `**Followers**: ${payload.followers}`,
      `**Top Languages**: ${payload.topLanguages.join(', ')}`,
      `**Signal**: ${payload.signalType} — ${payload.signalContext}`,
    ].filter(Boolean).join('\n');

    const mutation = `
      mutation CreateIssue($input: IssueCreateInput!) {
        issueCreate(input: $input) {
          success
          issue { id identifier url }
        }
      }
    `;

    const res = await fetch('https://api.linear.app/graphql', {
      method: 'POST',
      headers: {
        Authorization: env.LINEAR_API_KEY,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({
        query: mutation,
        variables: {
          input: {
            teamId: env.LINEAR_TEAM_ID,
            title: `${payload.leadName} (${payload.company ?? payload.githubUsername})`,
            description,
            priority,
            labelIds: [env.LINEAR_LEAD_LABEL_ID],
          },
        },
      }),
    });

    const data: any = await res.json();
    return Response.json({ ok: true, issue: data.data?.issueCreate?.issue });
  },
};

Setting Up the Pipeline in Linear

1. Create a 'GTM' or 'Leads' team in Linear — separate from your engineering team
2. Add workflow states: New Lead → Contacted → Qualified → Closed Won / Closed Lost
3. Create a 'GitHub Lead' label to identify GitLeads-sourced issues at a glance
4. Create a Linear API key at linear.app/settings/api and grab your team ID from the API
5. Deploy the Cloudflare Worker above and paste its URL as a GitLeads webhook destination
6. Configure GitLeads to track competitor repos or keywords relevant to your ICP

Alternative: Route via n8n or Zapier

If you prefer a no-code approach, GitLeads supports Zapier, n8n, and Make natively. Both Zapier and n8n have first-class Linear integrations. Set the trigger to GitLeads webhook, add a Linear "Create Issue" action, and map the lead fields. No code required.