LEAD GENERATION

Enrich and warehouse every GitHub stargazer to BigQuery for ICP analytics

Continuously capture each new stargazer, enrich their profile and company, compute an ICP fit score, and append the full record to BigQuery for funnel reporting and segmentation.

CategoryLead Generation
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitHub star event on repoGitHubGitHub
  • ActionFetch stargazer profile + activityGitHubGitHub
  • ActionEnrich company firmographics via ExaExa
  • LogicCompute ICP score + normalize to schema
  • OutputAppend enriched row to BigQueryGoogle BigQueryBigQuery

What it does

Builds a durable analytics layer on top of your stargazer signal. Every new star is enriched and scored, then written as a structured row to BigQuery — giving your team a queryable history of who's interested, how they score, and which repos and segments drive the best fits over time.

When to use it

You want to analyze stargazer trends, measure conversion by ICP segment, or feed a BI dashboard — not just react to individual stars. Best when an analyst or RevOps team owns the data and reps consume it downstream.

How it works

  1. 1A GitHub webhook fires on each new star event.
  2. 2The flow fetches the stargazer's GitHub profile, company, and activity stats.
  3. 3Exa enriches the company with firmographic and funding data.
  4. 4A scoring step computes an ICP fit score and segment label.
  5. 5A logic step normalizes the record into the warehouse schema.
  6. 6The enriched, scored row is appended to a BigQuery table for reporting and segmentation.

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 BigQueryDatasets, queries, schemas.
  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.