Auto-Check GitHub Stars for New Leads
When a new lead arrives in Salesforce, Notis checks if they've already starred your GitHub repo. It's a signal of existing interest before you reach out—skip the cold calls on warm leads.
Trigger
New Lead Trigger
Triggers when a new Lead is created in Salesforce.
Action
Check if repo starred by auth user
Use to determine if the authenticated user has starred a specific github repository, which is confirmed by an http 204 status (resulting in an empty dictionary in the response data); the action fails (e.g., http 404) if the repository is not starred or does not exist.
Why this helps
Reaching out to leads who already know and like your product feels redundant and wastes time on misaligned outreach.
- Identify leads with prior interest in your product via GitHub
- Personalize outreach based on GitHub engagement
- Reduce cold-call effort on already-warm leads
- Score leads automatically by repository engagement
Setup
Build it in a few focused steps.
- 1Connect Salesforce and GitHub to Notis
- 2Ask Notis: 'When a new lead is created in Salesforce, check if they've starred our [repo-name] on GitHub'
- 3Notis will cross-reference the lead's email or company domain with GitHub stargazers
- 4Specify what to do if they have starred (tag as 'warm lead', create a note, notify sales)
- 5Test by checking a known GitHub stargazer and creating them as a lead in Salesforce
Questions about this workflow
How does Notis match leads to GitHub users?
It uses email domain or company information from Salesforce to search GitHub stargazers. You can refine matching logic with Notis.
What if a lead used a personal email on GitHub but a company email in Salesforce?
This is a limitation—ask Notis if you want to handle this with manual list matching or additional checks.
Can this work backwards (GitHub stars → Salesforce leads)?
Yes. You can ask Notis to create the inverse: when someone stars your repo, auto-create a lead in Salesforce.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Salesforce to GitHub. A trigger fires from one place; an action lands in another.
Salesforce triggers
GitHub actions
Account Created or Updated
Triggers when an Account is created or updated in Salesforce. Uses LastModifiedDate high-watermark to capture both creations and updates.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Contact Updated
Triggers when an existing Salesforce Contact record is modified. Emits changed fields alongside relevant timestamps.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
Record Updated (Generic SObject)
Triggers when monitored fields change on any Salesforce SObject. You specify the SObject type and which field values should be returned in the payload. The trigger uses SystemModstamp to detect changes regardless of which specific field changed.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
New Contact Trigger
Triggers when a new Contact is Created in Salesforce.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
New Lead Trigger
Triggers when a new Lead is created in Salesforce.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
New or Updated Opportunity
Triggers when a Salesforce Opportunity is created or updated.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Task Created or Completed
Triggers when a Task is created or when its status changes to Completed in Salesforce. Supports optional filtering by task Status or Subject.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Salesforce and GitHub. Any combination from 985+ 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 GitHub.