Route heavy SEO jobs to the runner built for them
When a trusted webhook activates a crawl-intensive Semrush project, Notis appends the approved custom labels to the active GitHub repository runner.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add runner labels
Adds and appends custom labels to a self-hosted repository runner, which must be registered and active.
Why this helps
Resource-heavy crawl and reporting jobs can land on the wrong runner because infrastructure labeling was left as a separate setup task.
- Makes dedicated SEO capacity addressable in workflows
- Avoids repetitive runner settings work
- Appends labels without removing existing ones
Setup
Build it in a few focused steps.
- 1Connect Semrush and GitHub to Notis once and register the repository's self-hosted runner.
- 2Ask Notis to append the approved SEO workload labels when a trusted webhook activates a crawl-intensive Semrush project.
- 3Choose an incoming webhook trigger and an infrastructure report channel.
- 4Test with an active non-production runner and a harmless custom label.
Questions about this workflow
Will existing runner labels be removed?
No. This action appends new custom labels and ignores duplicates.
Can it label an offline runner?
The intended target is a registered, active self-hosted repository runner.
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.