LEAD GENERATION

Daily Slack digest of high-fit GitHub stargazers for the sales team

Each morning, pull the last 24 hours of stargazers across your repos, enrich and rank them by ICP fit, and post a ranked digest to a Slack channel so reps can prioritize outreach.

CategoryLead Generation
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionList stargazers from last 24h across reposGitHubGitHub
  • ActionEnrich profiles + companies via ExaExa
  • LogicRank by ICP fit, keep top N
  • OutputPost ranked digest to SlackSlack

What it does

Gives your sales team a once-a-day, ranked list of the most promising people who starred your repos overnight. Instead of watching GitHub all day, reps open Slack and see the top accounts with who they are, where they work, and why they scored well.

When to use it

Your stars trickle in around the clock and you want a low-noise, batched view rather than a real-time ping for every star. Ideal for a small sales or developer-relations team running daily outreach.

How it works

  1. 1A scheduled trigger runs every morning.
  2. 2The flow lists all stargazers added in the trailing 24 hours across your tracked repos.
  3. 3Each profile is enriched via GitHub, and Exa adds company firmographics.
  4. 4A scoring step ranks the batch by ICP fit and keeps the top N.
  5. 5The ranked shortlist is formatted into a readable digest with profile links and scores.
  6. 6The digest posts to your sales Slack channel as a single threaded message.

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 SlackChannels, DMs, threads, mentions.
  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.