Clear a GitHub Actions cache when browser checks point to stale data
Let a recurring browser check flag a cache problem, then ask Notis to clear the matching GitHub Actions cache by 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
A browser check can reveal stale cached output, but finding and clearing the affected cache adds another manual step.
- Review browser checks on a recurring schedule.
- Clear a cache only when the observed result supports it.
- Target a cache key and optionally a Git ref supplied in the check context.
Setup
Build it in a few focused steps.
- 1Connect Browserbase and GitHub once in Notis.
- 2Create an automation in plain language or in Automations, New Automation.
- 3In one instruction, ask Notis to review the scheduled browser result and clear the specified GitHub Actions cache only when the evidence indicates it is stale or corrupted.
- 4Choose a recurring schedule as the trigger.
- 5Choose a run report destination, then test with one real check result and cache key.
Questions about this workflow
Does the action clear every cache in the repository?
No. It deletes caches matching the specified key and optional Git ref. Supply those details in the instruction context.
What if no cache matches?
The action succeeds even if there are no matching caches to delete.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserbase tool to GitHub. A trigger fires from one place; an action lands in another.
Browserbase tool 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.
Browserbase tool 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.