Give the approved SEO app the branch access it needs
After your Semrush validation app is installed and approved, Notis applies the exact GitHub App restriction list to the named protected branch.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A release validation app can be fully configured yet blocked by branch restrictions, creating a difficult-to-trace failure.
- Removes a hidden release setup blocker
- Keeps the allowed app list explicit
- Creates a report for a sensitive configuration change
Setup
Build it in a few focused steps.
- 1Connect Semrush and GitHub to Notis once and confirm the validation app is installed with contents write permission.
- 2Tell Notis to replace app restrictions on the named protected branch with the exact approved app slug list after a trusted webhook.
- 3Choose an incoming webhook trigger and a secure channel for change reports.
- 4Test on a non-production protected branch before using the production rule.
Questions about this workflow
Does this append one app to the current list?
No. GitHub replaces the app restriction list, so the prompt and approved webhook must contain the complete intended list.
What does the app need first?
It must be installed and have contents write permission.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Semrush and GitHub, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.