Keep GitHub Actions Caches Fresh Automatically
Every Friday evening, Notis automatically clears stale GitHub Actions caches by key—freeing storage, preventing outdated dependencies, and eliminating the mental task of remembering cache maintenance.
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 accumulate, storage bloats, builds pull stale dependencies and fail cryptically; you forget to clear caches until the bill is due or debugging goes sideways.
- Caches are automatically cleared on schedule—no manual intervention
- Storage costs stay predictable and low
- Builds always use fresh dependencies, reducing mysterious failures
- One less recurring maintenance task your brain needs to track
Setup
Build it in a few focused steps.
- 1Connect GitHub to Notis.
- 2Create a cron automation: 'Every Friday at 6 PM, clear GitHub Actions caches for repository [repo-name] with key [cache-key-pattern]'.
- 3Tell Notis which caches to prioritize: 'clear build caches if older than 30 days, npm caches if older than 7 days'.
- 4Set Slack notifications to confirm each cleanup run.
Questions about this workflow
Can I run this more frequently?
Yes. Tell Notis: 'clear caches every Tuesday and Friday' or 'clear caches daily at midnight'. You set the frequency.
Will this clear caches I still need?
No. You specify the exact cache keys to clear. For example: 'clear caches matching temp-* but keep production-*'. Notis only removes what you explicitly name.
Can I clear caches by age instead of name?
Yes. Tell Notis: 'clear any cache older than 14 days'. Notis will track creation dates and remove old ones automatically.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to GitHub. A trigger fires from one place; an action lands in another.
Stripe triggers
GitHub actions
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
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.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Product Created Trigger
Triggered when a product is created in Stripe
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.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
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.
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
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 Stripe 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.