Auto-Create and Label Issues for New Leads
Every new lead in Salesforce becomes a labeled GitHub issue in seconds—no copy-pasting, no manual tracking, no forgotten prospects. Your engineering team stays informed without context-switching.
Trigger
New Lead Trigger
Triggers when a new Lead is created in Salesforce.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
New leads get lost between Salesforce and your engineering backlog, leaving engineers unaware of time-sensitive customer work.
- Leads appear automatically in your GitHub workflow without manual steps
- Engineers see prospect context without checking Salesforce
- Labels segment incoming leads (beta requests, integrations, feature requests)
- Eliminates forgotten or delayed feature requests
Setup
Build it in a few focused steps.
- 1Connect Salesforce and GitHub organizations to Notis
- 2Ask Notis: 'When a new lead is created in Salesforce, create a GitHub issue and label it as a lead inquiry'
- 3Specify the repository where issues should land and which labels apply
- 4Choose where Notis sends run confirmations (Slack, email, etc.)
- 5Test by creating a lead in Salesforce and verify an issue appears in GitHub within 1 minute
Questions about this workflow
Will this create duplicate issues if the same lead is entered twice?
Each Salesforce lead trigger creates one issue. If you create a duplicate lead record, you'll get a duplicate issue—ask Notis to add deduplication if you want to prevent that.
Can I customize the issue title and description based on lead data?
Yes. Notis will pull lead name, company, and source into the issue automatically.
What labels should I use?
Common ones: 'lead', 'sales-inquiry', 'feature-request', or 'integration-request'. Ask Notis to suggest labels based on your lead types.
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.