LEAD GENERATION

Score new GitHub stargazers and push qualified ICP matches to HubSpot

When someone stars your developer-tool repo, enrich their public GitHub and company profile, score the fit against your ICP.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitHub star (watch) event on repoGitHubGitHub
  • ActionFetch stargazer GitHub profile + companyGitHubGitHub
  • ActionEnrich company domain with ExaExa
  • LogicCompute ICP fit score
  • LogicDrop leads below score threshold
  • OutputUpsert qualified contact in HubSpotHubSpotHubSpot

What it does

Turns a raw GitHub star into a scored, enriched lead in HubSpot. Each new stargazer is enriched from their public GitHub profile and company, scored against your ideal-customer profile (company size, tech stack, role signals), and only qualified leads land in your CRM — so reps see real prospects, not hobbyists.

When to use it

You sell a developer tool and your repo stars are a top-of-funnel signal, but most stargazers are individual devs or students. Use this to separate buyers from browsers automatically and keep HubSpot clean.

How it works

  1. 1A GitHub webhook fires on the `watch` (star) event for your repo.
  2. 2The flow fetches the stargazer's public GitHub profile, bio, company, and follower count.
  3. 3Exa enriches the company domain with employee count, funding, and industry signals.
  4. 4A scoring step weighs ICP signals into a 0-100 fit score.
  5. 5A logic gate drops anyone below your threshold.
  6. 6Qualified leads upsert as a HubSpot contact with the score, source repo, and enrichment notes attached.

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 HubSpotCRM, deals, marketing, support.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.