LEAD GENERATION

Daily digest of new stargazers grouped by company to Slack

Once a day, pulls everyone who starred your repo in the last 24 hours, groups them by employer.

CategoryLead Generation
Enginesim
Difficultybeginner
Triggerschedule
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule (morning)
  • ActionFetch last-24h stargazersGitHubGitHub
  • LogicGroup and rank by company
  • OutputPost ranked digest to Slack channelSlack

What it does

Instead of per-star noise, this produces one clean daily summary. It collects the last day of new stargazers, clusters them by the company on their profile, counts how many engineers from each org starred, and posts a ranked list to a Slack channel. Companies with multiple stargazers float to the top as the strongest accounts.

When to use it

Use this when per-event alerts would be too noisy but you still want a daily pulse on which companies are paying attention to your project. Great for a #growth or #sales-signals channel.

How it works

  1. 1A daily schedule kicks off the run each morning.
  2. 2The flow fetches all stargazers added in the trailing 24 hours from GitHub.
  3. 3Stargazers are grouped by their org/company field and counted.
  4. 4A ranking step sorts orgs by stargazer count, then recency.
  5. 5The formatted digest is posted to the chosen Slack channel as a single message.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.