Turn New GitHub Stars Into Qualified Lead Context
Capture meaningful product interest while it is still fresh.
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
Get Lead Detail
Tool to fetch detailed information about a lead based on filters. Use when you need comprehensive lead data for a specific lead ID. The default view type is B2B. Note: On initial pageview, there may be a few seconds overhead before data is populated; consider implementing a 3-second delay after lead creation.
Why this helps
Founders notice repository stars late and lose the context needed for a thoughtful follow-up.
- Surfaces company and visitor context around new stars
- Reduces manual prospect research
- Creates a timely follow-up signal
Setup
Build it in a few focused steps.
- 1Connect GitHub and LeadBoxer to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it in plain language.
- 3Use this instruction: “When a new star is added to this repository, retrieve the matching LeadBoxer lead details and summarize the useful qualification context.”
- 4Select the GitHub New Stargazer Added trigger and choose a channel for run reports.
- 5Test it with one real repository star.
Questions about this workflow
Does this contact every stargazer?
It runs for each new stargazer detected on the monitored repository and asks LeadBoxer for matching lead details.
What if there is no matching lead?
Notis can report that no matching LeadBoxer record was found so the result is still clear.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to LeadBoxer. A trigger fires from one place; an action lands in another.
GitHub triggers
LeadBoxer 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.
Add or Update Lead Tags
Tool to add or update lead tags in LeadBoxer. Use when you need to manage lead tags by adding new tags, removing specific tags, or overwriting all existing tags for a specified user.
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 Custom Tracking Domain
Tool to delete a custom tracking domain entry for a dataset. Use when you need to remove a specific custom tracking domain (CTD) associated with a dataset in LeadBoxer.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Events
Tool to fetch events for specified sessions from LeadBoxer. Use when you need to retrieve behavioral data including pageviews, clicks, form submissions, email interactions, and custom events. Events can be filtered by session ID, email, user ID, or segment/smartlist IDs.
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 Lead Score Formula
Tool to fetch the lead score formula for a specific dataset. Use when you need to understand how lead scores are calculated for records in a dataset. The formula defines scoring based on criteria types: Range (number ranges), Match (exact values), Exists (presence of values), and Boost (event-based scoring).
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 Sessions
Tool to fetch sessions for a specified lead ID from LeadBoxer. Use when you need to retrieve session data for a user, with optional filtering by email, user ID, Smartlist ID, or segment ID. A session represents a single visit to the site, and users can have multiple sessions over time.
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.
Log Server-Side Event
Tool to track server-side events in LeadBoxer. Use when tracking backend events, page views, or custom activities from your server. This endpoint supports tracking user interactions, conversions, and other activities that occur on the server-side.
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 Custom Tracking Domains
Tool to fetch custom tracking domain entries for a dataset. Use when you need to retrieve all custom tracking domains that are created or in progress for a specific datasetId.
Commit Event
Triggered when a new commit is pushed to a repository.
Post Event Data
Tool to send event data for tracking user activities via POST request. Use when tracking events by sending data in the request body with application/x-www-form-urlencoded format.
Connect any two apps with Notis in the middle.
Not just GitHub and LeadBoxer. 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 LeadBoxer.