LEAD GENERATION

Repo Forker ICP Scorer to Airtable Pipeline

Collects engineers who fork your repo, enriches and scores their company against your ICP using an LLM.

CategoryLead Generation
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled harvest run
  • ActionPull new forks from GitHubGitHubGitHub
  • ActionEnrich forker company via web searchExa
  • ActionScore account fit against ICPOpenAI
  • LogicBranch on ICP fit threshold
  • OutputHigh-fit to pipeline, rest to nurture baseAirtableAirtable

What it does

Forking a repo is a stronger buying signal than starring it: the engineer intends to build on your code. This workflow harvests new forkers, enriches each one's company via a web search, and uses an LLM to score the account against your ideal-customer profile. High-fit accounts go straight to your Airtable sales pipeline; the rest are filed for nurture.

When to use it

Use it when fork volume is meaningful and you want only ICP-matched accounts reaching reps, with everything else retained for later marketing instead of discarded.

How it works

  1. 1A scheduled run kicks off the harvest.
  2. 2Pull forks created since the last checkpoint from the GitHub API.
  3. 3Enrich each forker's company with an Exa web search for domain, size, and industry.
  4. 4Score the account against your ICP rules with an OpenAI call, returning a fit score and rationale.
  5. 5Branch on the score threshold.
  6. 6Write high-fit accounts to the Airtable pipeline table with score and reason; route low-fit accounts to a separate nurture base.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect ExaNeural search across the web.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect AirtableBases, tables, views, automations.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.