Turn GitHub stargazers into ready-to-follow-up leads
A new star can be a warm signal. Let Notis capture it in Lemlist so promising interest does not disappear in a busy week.
Trigger
New Stargazer Added
Triggers when a new user stars a GitHub repository. Emits an event for each new stargazer detected on the monitored repository.
Action
Add Variables to Lead
Tool to add one or more variables to a lead. use when you need to enrich a lead with custom data after its creation or retrieval.
Why this helps
Founders notice stars too late and lose the moment to follow up.
- Preserves context around new product interest
- Reduces manual lead research
- Creates a dependable follow-up habit
Setup
Build it in a few focused steps.
- 1Connect GitHub and Lemlist to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language to enrich the matching Lemlist lead when a GitHub star appears.
- 3Select the GitHub New Stargazer Added trigger and choose where run reports should be sent.
- 4Test it with one real repository star.
Questions about this workflow
Does this send a campaign automatically?
No. It enriches the matching Lemlist lead so you can decide the next outreach step.
What does Notis use as context?
It uses the GitHub star event and available repository and account context in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Lemlist. A trigger fires from one place; an action lands in another.
GitHub triggers
Lemlist actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Delete Schedule
Tool to delete a specific schedule by scheduleid. use when you need to remove a schedule permanently after confirming its id.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Delete Unsubscribed Email
Tool to delete an email from the unsubscribed list. use when restoring a subscriber who has opted back in and you need to remove them from the suppressed contacts.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Unsubscribe Lead From Campaign
Tool to unsubscribe a lead from a campaign. use when you need to stop further outreach by removing a lead from the specified campaign.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get All Webhooks
Tool to retrieve the list of all webhooks configured for the team. use when you need to sync or audit active webhooks.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Get Campaign By ID
Tool to retrieve a specific campaign by campaignid. use when you need detailed campaign information by id.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Start Campaign Export
Tool to start an asynchronous export of all campaign statistics (csv). use when you need to initiate a csv export for a given campaign and track its progress.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Get Campaign Export Status
Tool to check the status of an asynchronous campaign export. use after starting an export to poll until done or error.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Campaign Sequences
Tool to retrieve a list of all sequences for a campaign with steps and conditions. use after fetching campaign to inspect its nested sequences and branching rules.
Connect any two apps with Notis in the middle.
Not just GitHub and Lemlist. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Lemlist.