Auto-Route Builds to Correct Runners
Different tasks need different compute resources. When a Salesforce task is created, Notis automatically assigns GitHub runner labels so your CI/CD builds go to the right infrastructure—no manual routing, no bottlenecks.
Trigger
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.
Action
Add org runner labels
Adds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.
Why this helps
Builds get queued on wrong runners because task type and runner labels aren't connected, causing delays for high-priority work.
- Route builds to appropriate runners automatically based on task priority
- Prevent high-priority work from queuing on slow runners
- Distribute CI/CD load intelligently across your infrastructure
- Eliminate manual runner assignment steps
Setup
Build it in a few focused steps.
- 1Connect Salesforce and GitHub to Notis
- 2Ask Notis: 'When a task is created in Salesforce, assign GitHub runner labels based on the task priority'
- 3Map Salesforce task types or priorities to GitHub runner labels (e.g., 'high-priority' → 'fast-runner')
- 4Choose notification settings
- 5Test by creating a high-priority task in Salesforce and verify runner labels are assigned in GitHub
Questions about this workflow
What runner labels do we have?
Whatever you've defined in your GitHub organization (e.g., 'macos', 'linux', 'fast-runner', 'gpu-runner'). Ask Notis to list them.
Can multiple labels be assigned?
Yes. A task can get multiple labels for more specific runner routing.
What if the label doesn't exist?
GitHub won't recognize it. Ask Notis to only assign labels that already exist in your organization.
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 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 GitHub.