Keep protected branches aligned with Vercel
When the deployment gate changes, the branch rules should know about it too.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 Vercel checks can be reported but not enforced if branch protection is updated manually later or not at all.
- Keeps quality gates enforceable
- Reduces configuration drift
- Makes release policy more dependable
Setup
Build it in a few focused steps.
- 1Connect Vercel and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create one.
- 3Tell Notis: When a new Vercel release check webhook arrives, add that status context to the matching protected GitHub branch and report the update.
- 4Choose an incoming webhook trigger and a reporting channel, then test with one new check.
Questions about this workflow
What must already exist?
The branch must already be protected and the status context must have been reported previously.
Does this replace all branch protection rules?
No. It adds the specified status check contexts to the existing protected branch.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Vercel to GitHub. A trigger fires from one place; an action lands in another.
Vercel triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
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.
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.
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 Vercel 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.