Invite New Accounts as GitHub Repository Collaborators
Stop manually adding account stakeholders to your GitHub repos. When a new account enters Salesforce, Notis automatically invites them as collaborators, keeping your codebase accessible without the admin overhead.
Trigger
Account Created or Updated
Triggers when an Account is created or updated in Salesforce. Uses LastModifiedDate high-watermark to capture both creations and updates.
Action
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.
Why this helps
Forgetting to grant new accounts repository access, leading to communication delays and repeated access requests.
- New accounts get instant repository access without manual intervention
- Reduces context-switching between Salesforce and GitHub
- Eliminates forgotten access grant steps that pile up
- Creates single source of truth for partner relationships
Setup
Build it in a few focused steps.
- 1Connect your Salesforce account to Notis via the portal (one-time setup)
- 2Connect your GitHub organization account to Notis (one-time setup)
- 3Ask Notis: 'When a new account is created in Salesforce, invite them as a collaborator on [your-repo-name] in GitHub'
- 4Notis will set the trigger to 'Account Created or Updated' and ask you where to report runs (Slack, email, or your chosen channel)
- 5Test by creating a test account in Salesforce and verify it receives a GitHub invitation within 2 minutes
Questions about this workflow
Will this send invitations to existing accounts if Salesforce data gets updated?
Yes. This workflow triggers on account creation AND updates, so if you modify an account record, it will send an invitation. You can ask Notis to refine it to 'only new accounts' if you prefer.
What if an account already has GitHub access?
GitHub will recognize they already have collaborator status and the invitation will be idempotent (no duplicate access granted).
Can I apply this to multiple repositories at once?
Yes. You can ask Notis to run this for multiple repos, or create separate automations for each repo you want to keep synced.
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.