Tracks GitHub stars and sends Slack notifications for new stargazers.

GitHub stargazers are one of the most valuable intent signals for finding qualified leads within developer communities.

It's a great place to find prospective customers or even people to hire, within people who already care about your solution or your problem area.

You can get notified of new stargazers for your own repos, or your competitors' repos.

[INSERT IMAGE OF WHAT THIS LOOKS LIKE]

• Remix this val, and add your SLACK_WEBHOOK_URL to your environment variables on the left sidebar (Guide)
• Configure the repos you want to track in cron.ts. It'll auto-run every 15 minutes.

If you're only interested in getting notified about your own stargazers, you can set up a webhook in GitHub and route events to your Slack.

However, to backfill stargazers from the past, or to track competitors' repos, it's a little more tricky due to 2 things:

1. GitHub's stargazer API does not return emails for users out-of-the-box. We work around this by looking up the stargazers' past commits. GitHub commits are associated with emails. It's not technically private, but it is harder to find.
2. It's hard to get notified about competitors' stargazers because you can't set up webhooks for repos you don't own. GitHub's stargazer API also happens to return stargazers from oldest to newest / FILO. So you want to calculate the last page of results and start from there. You can use crons and blob storage in Val Town to keep track of the stargazer count every 15 mins. When that count changes by X, then go to the last page of stargazers and grab the last X users to get notified.

• Enrich this data through Clay and funnel leads within your ICP directly to a #VIP-leads channel