Clear the cache CircleCI identified as corrupted
When a CircleCI run points to a corrupted GitHub Actions cache, let Notis remove the matching cache key and report what it cleared.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Cache failures send you searching through run logs and GitHub settings to find and remove the right entry.
- Reduce manual cache troubleshooting
- Act only on a cache key found in the CircleCI report
- Get a run report with the key that was cleared
Setup
Build it in a few focused steps.
- 1Connect CircleCI and GitHub once in Notis.
- 2Create an automation in Notis and give it a clear name.
- 3In one instruction, tell Notis to inspect the CircleCI failure details and clear the matching GitHub Actions cache only when a specific cache key is present.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real CircleCI failure that identifies a cache key.
Questions about this workflow
Does this clear every cache in the repository?
No. Instruct Notis to use the specific key identified in the CircleCI failure and avoid clearing a cache when the key is missing or ambiguous.
What should the webhook include?
Send the CircleCI run details or a link and enough diagnostic information for Notis to identify the affected GitHub repository and cache key.
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.