Give every critical SEO alert a clear owner
When your Semrush alerting process calls Notis, the matching GitHub issue is assigned immediately using the ownership rules in your prompt.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Urgent SEO alerts often sit unowned until someone notices, interprets them, and finds the right engineer.
- Creates immediate accountability for critical findings
- Cuts the handoff between growth and engineering
- Reduces follow-up messages and mental tracking
Setup
Build it in a few focused steps.
- 1Connect Semrush and GitHub to Notis once.
- 2Create an automation with a prompt that assigns matching GitHub issues when a critical Semrush finding arrives.
- 3Choose an incoming webhook trigger and select the channel for run reports.
- 4Send one real critical finding to the webhook and confirm the expected assignee.
Questions about this workflow
How does Notis know whom to assign?
Describe simple ownership rules in the prompt, such as repository area, issue label, or named fallback owner.
What if no matching issue exists?
Notis can report the unmatched finding in your chosen channel instead of assigning the wrong issue.
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.