Track GitHub Issues as Salesforce Leads
New GitHub issues become leads instantly. No more switching between platforms to track customer feedback.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
Create lead
Creates a new lead in salesforce with the specified information.
Why this helps
When customer issues come in via GitHub, you either manually enter them into Salesforce or they slip through the cracks entirely. By the time you remember, context is lost.
- Every GitHub issue automatically becomes a trackable lead in Salesforce
- Eliminates manual data entry between platforms
- Ensures customer feedback is captured in your CRM
- Reduces follow-up delays
Setup
Build it in a few focused steps.
- 1Connect GitHub and Salesforce to Notis (one-time setup in the Notis portal).
- 2In the Notis portal, go to Automations > New Automation and create a workflow named 'GitHub Issues to Leads'.
- 3Set the prompt to: 'When a new GitHub issue is created, create a matching lead in Salesforce with the issue title as the company name and issue URL in the description.'
- 4Choose 'GitHub: New Issue Created' as the trigger and select your communication channel for run notifications.
- 5Test with one real GitHub issue to confirm the lead appears in Salesforce.
Questions about this workflow
Will this create a new lead for every single issue?
By default, yes. You can refine the automation in Notis to filter by labels (e.g., only 'customer-request' labels) if needed.
Can I map issue fields to specific lead fields?
Notis handles field mapping automatically based on your plain-language instruction. You don't configure individual field mappings. If you want custom mapping, just describe it to Notis and it will interpret your intent.
What happens if the same issue is updated?
This workflow triggers on new issues only. If you want to track updates to existing issues, ask Notis to create a separate automation for 'Issue Updated' events.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Salesforce. A trigger fires from one place; an action lands in another.
GitHub triggers
Salesforce 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.
Create Salesforce Account
Deprecated: creates a new salesforce account using a json post request, requiring 'name'; specific fields (e.g., custom, dunsnumber) may have org-level prerequisites.
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.
Add contact to campaign
Adds a contact to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Add lead to campaign
Adds a lead to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
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.
Add product to opportunity
Adds a product (line item) to an opportunity. the product must exist in a pricebook entry that's associated with the opportunity's pricebook.
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.
Apply lead assignment rules
Applies configured lead assignment rules to a specific lead, automatically routing it to the appropriate owner based on your organization's rules.
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.
Associate contact to account
Associates a contact with an account by updating the contact's accountid field.
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.
Clone opportunity with products
Clones an opportunity and optionally its products (line items). creates a new opportunity with the same field values and products as the original.
Commit Event
Triggered when a new commit is pushed to a repository.
Clone record
Creates a copy of an existing salesforce record by reading its data, removing system fields, and creating a new record. optionally apply field updates to the clone.
Connect any two apps with Notis in the middle.
Not just GitHub and Salesforce. 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 Salesforce.