Make your Semrush validation part of branch protection
Once your SEO check context has reported successfully, an approved setup webhook tells Notis to add it to the chosen protected branch.
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
Teams remember to run SEO checks inconsistently when the validation is documented but not attached to the release path.
- Moves SEO validation into the normal release flow
- Reduces reliance on release-day memory
- Applies a consistent check to the intended branch
Setup
Build it in a few focused steps.
- 1Connect Semrush and GitHub to Notis once and ensure the SEO status context has already reported on the repository.
- 2Tell Notis to add that exact Semrush validation context to the named protected branch after an approved setup webhook.
- 3Choose an incoming webhook trigger and a channel for configuration reports.
- 4Test on a non-production protected branch with the real reported context.
Questions about this workflow
Can Notis add a context that has never reported?
No. GitHub requires the status check context to have been reported previously.
Does this replace existing required checks?
This action adds the named contexts; describe the exact branch and contexts in the prompt to keep the change bounded.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Semrush to GitHub. A trigger fires from one place; an action lands in another.
Semrush 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 Semrush 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.