Provision the shared variable every SEO workflow expects
Notis receives the approved Semrush project repository and grants it access to the existing selected-repository GitHub Actions variable.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add selected repository to an organization variable
Grants a repository access to an organization-level github actions variable, if that variable's visibility is set to 'selected repositories'.
Why this helps
A repository can miss a shared non-secret setting and fail later, leaving the founder to reconstruct a forgotten setup step.
- Standardizes repository setup
- Avoids repetitive settings work
- Limits access to approved repositories
Setup
Build it in a few focused steps.
- 1Connect Semrush and GitHub to Notis once and create the organization variable with selected-repository visibility.
- 2Ask Notis to grant each approved new Semrush project repository access to that exact GitHub Actions variable.
- 3Select an incoming webhook trigger and a channel for provisioning reports.
- 4Test with a sandbox repository from the same organization.
Questions about this workflow
Can this create the organization variable?
No. The variable must already exist and use selected-repository visibility.
Is this suitable for secrets?
This workflow is for an organization variable. Use the corresponding secret-access workflow for sensitive values.
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.