Stargazers for your competitor's repos are qualified leads hiding in plain sight.

Sends Slack notifications for new GitHub repo stargazers

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

It's an especially great place to find:

1. Prospective customers
2. People to hire!

These are people who already care about your solution or your problem area.

If you're not already getting notified of new stargazers for your own repos, or your competitors' repos - you can easily do this up today.

• 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 get notified every time someone new stars your repo.

However, there are 2 major limitations to that:

1. You can't backfill stargazers from the past - which are often incredibly valuable to folks trying to find qualified leads!
2. You can only set up webhooks for repos that you own.

This val does 2 things for you:

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. They're 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 doesn't let you sort by starred_at times easily and are fetched from oldest to newest. So to get the most recent stargazers, we 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, go to the last page of stargazers and grab the last X users to get notified.

This is a great way to get notified about new stargazers across many repos - regardless of whether you own them or not.

• Make a pit stop between GitHub -> Slack and send this data through Clay to funnel ICP leads directly to a #VIP-leads channel! (Guide coming soon)