Clear a targeted GitHub Actions cache after a Bolna failure
Use the failure context to remove a cache entry that is suspected to be outdated or corrupted.
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
When a build failure points to stale cache data, finding and clearing the right entry adds friction to the recovery loop.
- Clear a specific cache key from the affected repository.
- Optionally scope cache removal to a Git ref.
- Reduce manual cleanup steps after a suspected cache issue.
Setup
Build it in a few focused steps.
- 1Connect Bolna and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to clear the specified GitHub repository cache key, and optional ref, when a Bolna failure webhook identifies stale or corrupted cache data.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real failure event and a cache key safe to remove.
Questions about this workflow
Does the event need to include a cache key?
Yes. Provide the repository and key in the webhook context, and include a ref if cleanup should be scoped.
What happens if no matching cache exists?
The GitHub action succeeds even when it finds no matching cache to delete.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bolna to GitHub. A trigger fires from one place; an action lands in another.
Bolna 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.
Bolna 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.