Clear GitHub cache after Rafflys campaign updates
A campaign update should not be confused by an old build cache. Notis can clear the designated GitHub cache as soon as Rafflys signals the change.
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
Stale cached assets can make a campaign update look unreliable and take time to diagnose.
- Prevents repeated cache troubleshooting
- Makes campaign updates more predictable
Setup
Build it in a few focused steps.
- 1Connect Rafflys and GitHub to Notis once.
- 2Create a webhook-triggered automation.
- 3Write an instruction to clear the named GitHub Actions cache when Rafflys reports a campaign configuration update.
- 4Choose a reporting channel and test with a safe cache key.
Questions about this workflow
Will it delete source code?
No. It only clears the selected GitHub Actions cache.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Rafflys to GitHub. A trigger fires from one place; an action lands in another.
Rafflys triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Rafflys and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.