Clear the stale build cache tied to a CDN refresh
Send the refresh context and cache identifier to Notis, then remove the GitHub Actions cache that is tied to that stale build.
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
A CDN refresh may not resolve stale build output if a later build keeps reusing an outdated actions cache.
- Tie cache cleanup to a specific refresh request.
- Use targeted key and optional ref details.
- Reduce repeated stale artifact troubleshooting.
Setup
Build it in a few focused steps.
- 1Connect BunnyCDN and GitHub once in Notis.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis to clear the specified GitHub repository cache key and optional ref supplied with the BunnyCDN refresh webhook.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real refresh request and verify the cache target.
Questions about this workflow
Does a BunnyCDN purge automatically provide GitHub cache information?
No such trigger data is listed. The webhook must include or reference the repository, cache key, and optional ref to clear.
Can this clear every cache in a repository?
The supplied action is for a cache matching a key and optional ref. It should be used with a specific target.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bunnycdn to GitHub. A trigger fires from one place; an action lands in another.
Bunnycdn 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.
Bunnycdn 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.