Remove access chasing from SEO consultant onboarding
When your onboarding backend sends an approved Semrush project request, Notis adds the named consultant to the specified GitHub repository with the permitted role.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
External SEO work stalls while access requests bounce between project notes, messages, and repository settings.
- Shortens consultant onboarding
- Keeps repository and permission scope explicit
- Reports every access change in one channel
Setup
Build it in a few focused steps.
- 1Connect Semrush and GitHub to Notis once.
- 2Create an automation that adds only an approved consultant from your Semrush project onboarding webhook to the named repository with the stated permission.
- 3Select an incoming webhook trigger and an access-report channel.
- 4Test with a trusted account and a sandbox repository.
Questions about this workflow
Can this grant admin access?
The action supports repository permissions for organization-owned repositories, but the prompt should grant only the minimum approved level.
What if the person is already a collaborator?
GitHub updates their permission to the requested level instead of creating a duplicate collaborator.
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.