Auto-Grant Secret Access on Onboarding
New team members shouldn't wait for secret provisioning. When a contact joins in Salesforce, Notis automatically grants them access to organization secrets in GitHub—so they can deploy on day one without asking for credentials.
Trigger
New Contact Trigger
Triggers when a new Contact is Created in Salesforce.
Action
Add selected repository to an organization secret
Adds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.
Why this helps
New developers are blocked from deployments because they don't have access to deploy secrets, causing onboarding delays.
- New contacts get secret access automatically on day one
- Eliminate deployment blockers during onboarding
- Reduce manual secret provisioning steps
- Automate credential access across your organization
Setup
Build it in a few focused steps.
- 1Connect Salesforce and GitHub to Notis
- 2Ask Notis: 'When a new contact is created in Salesforce, grant them access to our organization secrets in GitHub'
- 3Specify which organization secrets to grant access to (e.g., deploy credentials, API keys)
- 4Choose notification settings
- 5Test by creating a new contact in Salesforce and verify they get secret access in GitHub
Questions about this workflow
Which secrets should a new contact have access to?
That depends on their role. Ask Notis to map role to secrets (e.g., developers get 'DEPLOY_KEY', admins get everything).
What if they join multiple teams?
Ask Notis to grant secrets based on team membership so they get the right access for their roles.
Can I revoke secret access when they leave?
Yes, set up a complementary automation that removes access when contacts are marked inactive.
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.