Clear an outdated GitHub Actions cache key on schedule
Set a recurring review and have Notis clear the repository cache key your team has identified for cleanup.
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
Caches flagged for cleanup can linger because someone has to remember the repository, key, and follow-up.
- Turn a recurring cleanup reminder into a reported action.
- Target a repository cache using a known key and optional git ref.
- The action succeeds even when no matching cache is found.
Setup
Build it in a few focused steps.
- 1Connect BotMape and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, tell Notis to clear only the cache key and repository your team has identified for cleanup.
- 4Pick the recurring schedule trigger and choose where run reports go.
- 5Test with one real repository and cache key before relying on the schedule.
Questions about this workflow
Does the action discover which cache is stale?
The available action deletes caches by a specified key and optional git ref. Supply the key and repository in the prompt or relevant input; do not assume BotMape provides a cache baseline.
What happens if there is no matching cache?
The GitHub action succeeds even if it finds no matching caches to delete.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BotMape to GitHub. A trigger fires from one place; an action lands in another.
BotMape 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.
BotMape 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.