Catch repeated cache failures before they keep interrupting work
Have Notis review recent CircleCI diagnostics on a schedule and clear a GitHub Actions cache only when the evidence points to one exact key.
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
The same cache issue can keep breaking runs because nobody has time to compare failures and clean up the stale entry.
- Group recurring cache symptoms into one review
- Avoid broad cache deletion
- Receive a report of the evidence and cleanup
Setup
Build it in a few focused steps.
- 1Connect CircleCI and GitHub once in Notis.
- 2Create a named automation and describe the review and cleanup in one instruction.
- 3Tell Notis to review recent CircleCI diagnostics, identify an exact repeatedly failing GitHub Actions cache key, and clear it only when the evidence is conclusive.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real set of CircleCI diagnostics that includes a known cache issue.
Questions about this workflow
What if the diagnostics do not name a cache key?
The instruction should have Notis report the issue without clearing a cache when no exact key can be established.
Does this require CircleCI to expose a native Notis trigger?
No. This workflow starts on a Notis schedule and asks Notis to review the available CircleCI run information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Circleci to GitHub. A trigger fires from one place; an action lands in another.
Circleci triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Circleci and GitHub, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.