A GitHub stargazer is a person who clicks Star on a GitHub repository. With a GitHub stargazers signal agent, lemlist watches up to 10 public repositories you choose and creates a contact each time a new stargazer can be identified. Use it to reach developers who just showed interest in a project in your space, such as your own repository or a competitor's.
Limitations
You can track up to 10 repositories per signal agent.
You can only track public GitHub repositories.
A stargazer becomes a contact only when their GitHub profile shows a personal LinkedIn profile or a valid public email address. This is the case for about 22% of stargazers, so many stars produce no contact.
Each signal agent is scanned once per hour. If a repository receives many stars between two scans, some stargazers can be missed.
Removing a star is not tracked. A contact created from a star stays in lemlist if the person later removes the star.
The signal agent identifies signals only up to the daily limit you set. Stars beyond that limit on the same day do not create contacts.
If the signal agent is paused for insufficient credits, it does not resume automatically when your Signals add-on credits are refilled.
Credits
GitHub stargazers costs 100 credits per signal identified. If your team has the Signals add-on, credits are taken from the Signals add-on first, then from your generic credits.
The daily limit you set in Identification limit caps the cost. For example, a limit of 5 signals per day costs at most 500 credits daily, 15,000 credits per month.
Phase 1: Select the GitHub stargazers signal
Open Signal agents from the left sidebar, then click Create signal agent.
In the Signal to detect step, open the Buyer intent category, or type GitHub in the Search signals, keyword, ... bar.
Select GitHub stargazers, then click Next.
Phase 2: Configure your signal
In Agent configuration, enter an Agent name.
In Repositories to monitor, paste the URL of each public repository in Repository URLs (one per line), for example
https://github.com/vercel/next.js.Click Add repositories.
✅ Verify: each repository appears in the list below with Valid, and the counter shows how many are added, for example 1/10 repository added.
In Identification limit, set the Maximum number of signals identified per day. Use the slider, pick 5, 20, or 50, or type a value in Enter amount. The maximum cost is shown under This will cost at most:.
Click Next.
Phase 3: Scope
In the Scope step, All contacts is the only option for GitHub stargazers. Click Next.
Phase 4: Decide how signals are processed
In Signals processing, choose one option:
Review signals manually: review and handle each signal yourself.
Auto-create tasks: lemlist creates a task for each signal.
Auto-push to campaign: lemlist enrolls the new contacts into a campaign.
If you choose Auto-push to campaign, pick one option in Campaign configuration:
AI-powered outreach: lemlist generates a campaign with AI-written copy. Choose a sequence type: Email sequence, LinkedIn first, or Multichannel + Cold call, then follow the steps.
Link to an existing campaign: connect the signals to a campaign you already created.
Click Next.
Phase 5: Review and deploy
In Summary, check Billing, Signals processing, and Scope.
Click Deploy agent.
✅ Verify: the GitHub stargazers signal agent appears in Signal agents.
What happens after you deploy
lemlist scans the tracked repositories once per hour. When a new stargazer has a personal LinkedIn profile or a valid public email address on their GitHub profile, lemlist creates a contact and processes it the way you chose in Signals processing. Stargazers without either are skipped.
Practical example
A company selling a developer tool tracks its own repository and two competitor repositories, with Auto-push to campaign selected. Each hour, new stargazers who can be identified are added as contacts and enrolled in the campaign, so outreach starts while the interest is recent.
Troubleshooting & pitfalls
Issue: A repository got new stars, but no contacts were created
Root cause: the stargazers' GitHub profiles do not show a personal LinkedIn profile or a valid public email address, the daily identification limit is reached, or the next hourly scan has not run yet.
Fix: wait at least one hour after the stars were added. Check the daily count in Identification limit (for example Today: 5 / 5 identified) and raise the limit if needed. Stars from profiles without a personal LinkedIn or a public email do not create contacts.
Issue: The signal agent stopped after I added credits
Root cause: a signal agent paused for insufficient credits does not resume automatically when the Signals add-on credits are refilled.
Fix: open the signal agent in Signal agents and check its status after adding credits.
For other cases where a signal agent shows no results, see Fix: Signal agents not returning results.
If your case is different
If you want to track companies visiting your website instead, see How to create Signal agent for website visitors.
For all available signal types and their credit costs, see Signal Agents overview.