LEAD GENERATION

Daily Stargazer Digest with Slack Routing

Once a day it collects new stargazers, scores them, and posts a ranked Slack digest that routes high-fit accounts to the sales channel and the rest to a watch list.

CategoryLead Generation
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionList new stargazers since last runGitHubGitHub
  • ActionFetch and score each profileGitHubGitHub
  • LogicRoute high-fit to sales, rest to watch list
  • OutputPost ranked digest to SlackSlack

What it does

Batches yesterday's new stars into one tidy Slack digest instead of a stream of noise. It scores each stargazer, ranks them, and routes the strongest fits to your sales channel with an @mention while parking lower-priority names on a watch list, so the team sees signal not volume.

When to use it

Use this when star velocity is high enough that per-star notifications become noise. Best for teams that want a once-a-day review ritual and a clear handoff between dev-rel and sales.

How it works

  1. 1A daily schedule fires each morning.
  2. 2The flow lists all stargazers added since the last run via the GitHub API.
  3. 3Each stargazer profile is fetched and scored on company presence, seniority signals, and reach.
  4. 4A routing step splits the list into high-fit (sales) and the rest (watch list).
  5. 5A formatting step builds a ranked digest with profile links and scores.
  6. 6The digest posts to Slack, mentioning the sales owner on the high-fit block.

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.