Clear stale GitHub caches when markets move
Stop wondering whether yesterday's cached result is still trustworthy.
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
Market-sensitive code can quietly reuse stale artifacts while the founder is focused elsewhere.
- Reduces manual cache housekeeping
- Keeps price-sensitive builds aligned with current conditions
- Creates a simple recurring safety net
Setup
Build it in a few focused steps.
- 1Connect Finage and GitHub to Notis once in the portal.
- 2Create an automation in the portal or ask Notis in plain language to clear the relevant GitHub Actions cache when Finage shows a material market move.
- 3Pick a recurring Notis schedule and choose the channel for run reports.
- 4Test it with one real market symbol and cache key.
Questions about this workflow
What does Notis use Finage for?
It checks the market data and decides whether the condition in your instruction is met before acting in GitHub.
Can I choose where run updates appear?
Yes. Select a reporting channel when creating the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Finage to GitHub. A trigger fires from one place; an action lands in another.
Finage 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 Finage 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.