Know which SEO fixes actually reached the finish line
Notis revisits the urgent Semrush findings on schedule, checks their referenced GitHub pull requests, and reports what is merged versus still open.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if pull request merged
Checks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).
Why this helps
A fix can look handled once a pull request exists even though it remains unmerged for days.
- Closes the gap between planned and shipped SEO work
- Creates a concise follow-up list
- Eliminates repeated pull request tab checks
Setup
Build it in a few focused steps.
- 1Connect Semrush and GitHub to Notis once.
- 2Ask Notis to review priority Semrush findings and check the merge status of each linked GitHub pull request.
- 3Choose a weekday schedule and the channel for the merge-status digest.
- 4Test with one merged and one open SEO pull request.
Questions about this workflow
Does this merge pull requests?
No. It only checks whether each specified pull request has merged and reports the result.
Can I limit the digest to critical fixes?
Yes. Describe the Semrush severity, project, or campaign scope in the 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.