Keep GitHub build caches from becoming invisible clutter
A small maintenance habit can prevent old caches from quietly consuming attention and storage.
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
Build-cache cleanup is easy to postpone because it competes with visible product work.
- Reduces maintenance decisions
- Keeps cache storage under control
- Turns reminders into an executable routine
Setup
Build it in a few focused steps.
- 1Connect Raindrop.io and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis for a scheduled cleanup automation.
- 3Write one instruction: On the schedule, review Raindrop maintenance notes and clear the specified stale GitHub repository cache when cleanup is due.
- 4Choose a recurring trigger, pick the channel for run reports, and test with one maintenance note.
Questions about this workflow
Can it clear every cache?
Specify the repository and cache key rules in the prompt so the cleanup remains deliberate.
Is this useful for small teams?
Yes. It turns a low-frequency task into a predictable background routine.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Raindrop.io to GitHub. A trigger fires from one place; an action lands in another.
Raindrop.io 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 Raindrop.io and GitHub. Any 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.