Skip to content
Notis

Auto-Enforce Status Checks for New Accounts

Compliance shouldn't be an afterthought. When a new account enters Salesforce, Notis automatically adds required status checks to their GitHub repositories—ensuring every deployment meets your standards from day one.

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 status check contexts

Adds status check contexts (provided in the request body, e.g., `{"contexts": ["new-context"]}`) to a protected branch, requiring these contexts to have been previously reported.

Why this helps

New partnerships skip compliance gates because setup is manual and easy to forget, leaving you with unvetted deployments.

  • Enforce compliance standards automatically for new accounts
  • Eliminate manual status check configuration
  • Reduce risk of unvetted deployments
  • Keep security gates consistent across all partnerships

Setup

Build it in a few focused steps.

  • 1Connect Salesforce and GitHub to Notis
  • 2Ask Notis: 'When a new account is created in Salesforce, add required status checks to their GitHub repositories for compliance'
  • 3Define which status checks are required (e.g., CI build, security scan, code review)
  • 4Select repositories and notification settings
  • 5Test by creating an account in Salesforce and verify status checks appear on the associated repo

Questions about this workflow

What status checks can be enforced?

Any status check already configured in GitHub (CI/CD, security scanners, code quality tools). You specify which ones.

Will this block existing PRs?

Adding new required checks may cause existing open PRs to fail until they satisfy the new requirements.

Can I make this conditional based on account type?

Yes. Ask Notis to apply different status checks based on account industry, size, or tier.

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.

TriggerPolling

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

Contact Updated

Triggers when an existing Salesforce Contact record is modified. Emits changed fields alongside relevant timestamps.

TriggerPolling

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.

ActionInstant

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.

TriggerPolling

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

New Contact Trigger

Triggers when a new Contact is Created in Salesforce.

TriggerPolling

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

New Lead Trigger

Triggers when a new Lead is created in Salesforce.

TriggerPolling

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.

ActionInstant

New or Updated Opportunity

Triggers when a Salesforce Opportunity is created or updated.

TriggerPolling

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.

ActionInstant

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.

TriggerPolling

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.

ActionInstant

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.

ActionInstant

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.