Catch broken SEO ownership before planning starts
Notis reviews the selected Semrush work and checks whether each planned teammate can actually be assigned to its GitHub issue.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if a user can be assigned to an issue
Checks if a specified github user can be assigned to a given issue within a repository.
Why this helps
A planning session loses momentum when the named owner lacks access or cannot be assigned to the issue.
- Prevents ownership surprises during planning
- Flags access gaps in one concise report
- Keeps the SEO handoff moving
Setup
Build it in a few focused steps.
- 1Connect Semrush and GitHub to Notis once.
- 2Create an automation asking Notis to review this week's Semrush priorities and check whether each planned owner can be assigned to its GitHub issue.
- 3Select a schedule before your weekly planning session and choose a report channel.
- 4Test the check with one valid assignee and one teammate without issue access.
Questions about this workflow
Does the check assign anyone?
No. It verifies whether a named user can be assigned to a specific issue so you can fix access first.
Can it use different owners by repository?
Yes. Put your repository ownership rules directly in the automation prompt.
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.