LEAD GENERATION

Weekly Stargazer Lead Digest to Airtable and Slack

On a weekly schedule, collects all new stargazers across your repos, enriches and dedupes them into an Airtable lead sheet.

CategoryLead Generation
Enginesim
Difficultybeginner
Triggerschedule
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionList new stargazers across reposGitHubGitHub
  • ActionEnrich stargazer companiesExa
  • LogicDedupe and rank by ICP fit
  • ActionWrite leads to Airtable baseAirtableAirtable
  • OutputPost ranked digest to SlackSlack

What it does

Once a week this workflow gathers every new stargazer since the last run, enriches each one with company data, writes deduped rows into an Airtable lead base, then posts a ranked summary of the strongest prospects into a Slack channel so reps can grab them.

When to use it

Use this when you don't need real-time alerts but want a steady, reviewable weekly pipeline of inbound interest. Ideal for small teams who triage leads in batches and live in Airtable plus Slack.

How it works

  1. 1A schedule trigger runs every Monday morning.
  2. 2A GitHub action lists new stargazers across the configured repos since the prior run.
  3. 3An Exa action enriches each stargazer's company with size, industry, and domain.
  4. 4A logic step dedupes against existing Airtable rows and ranks by ICP fit score.
  5. 5New and updated leads are written to the Airtable lead base with status New.
  6. 6A Slack message posts the top-ranked prospects as a claimable digest with links to each Airtable record.

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 AirtableBases, tables, views, automations.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  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.