LEAD GENERATION

Stargazer Enrichment Sync to BigQuery Warehouse

On a schedule, pulls the full current stargazer list, enriches new entries with company data, and upserts a clean.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionFetch current stargazer listGitHubGitHub
  • LogicDiff against warehouse table
  • ActionEnrich new stargazersExa
  • LogicNormalize + score fields
  • OutputUpsert rows into BigQueryGoogle BigQueryBigQuery

What it does

This workflow keeps a warehouse table of every enriched stargazer in sync. On each run it fetches the current stargazer list, enriches anyone new with firmographics, and upserts deduplicated rows into BigQuery so your data team can model lead quality and feed reverse-ETL pipelines.

When to use it

Use this when GitHub interest needs to live in the warehouse alongside product and revenue data, not just a CRM. Ideal for RevOps and data teams that drive routing and scoring from BigQuery rather than point tools.

How it works

  1. 1A schedule trigger runs daily.
  2. 2A GitHub action retrieves the complete current stargazer list for the repo.
  3. 3A logic step diffs against the existing BigQuery table to isolate new stargazers.
  4. 4An Exa action enriches only the new entries with company size, domain, and industry.
  5. 5A second logic step normalizes fields and computes a fit score column.
  6. 6An upsert action merges the enriched, deduped rows into the BigQuery lead table for downstream use.

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.