Clear the build cache behind recurring crawl problems
Notis checks the latest Semrush crawl on schedule and clears the approved GitHub Actions cache key when the anomaly matches your known stale-build pattern.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Clear repository cache by key
Deletes github actions caches from a repository matching a specific `key` and an optional git `ref`, used to manage storage or clear outdated/corrupted caches; the action succeeds even if no matching caches are found to delete.
Why this helps
Recurring stale metadata or generated pages can prompt the same investigation and cache cleanup again and again.
- Automates a well-understood recovery step
- Reduces repeated debugging of stale output
- Keeps cache deletion bounded to an approved key
Setup
Build it in a few focused steps.
- 1Connect Semrush and GitHub to Notis once.
- 2Ask Notis to check Semrush for your known crawl anomaly and clear only the approved GitHub Actions cache key when it appears.
- 3Pick a daily scheduled trigger and a channel for cleanup reports.
- 4Test with a disposable cache key and a real matching crawl example.
Questions about this workflow
Can this clear every repository cache?
The useful setup is deliberately narrow: identify the repository, cache key, and optional Git ref in the prompt.
What happens if the cache key is already gone?
GitHub treats the clear operation as successful even when no matching cache remains.
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.