Give payment operations a fresh cache
Clear a known Actions cache key on a recurring schedule when your payment operations process needs fresh cached results.
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
Old cached results can add confusion when payment operations rely on recurring automated checks.
- Removes a specified cache key on a cadence
- Cuts a recurring manual maintenance task
- Keeps the cleanup focused on the repository and ref you name
Setup
Build it in a few focused steps.
- 1Connect Airwallex and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation.
- 3Describe the repository cache cleanup, including the exact key and optional Git ref because the schedule does not provide them.
- 4Choose the recurring schedule and a report channel.
- 5Test once against a real cache key and confirm the expected cache is cleared.
Questions about this workflow
Does Airwallex start this workflow?
No. The trigger is a Notis schedule. The workflow is useful when your team wants scheduled cleanup for a cache used by its Airwallex payment operations process.
Can this refresh every cache in the repository?
The listed action deletes caches matching a specified key and optional ref. It does not provide a general clear-all action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Airwallex to GitHub. A trigger fires from one place; an action lands in another.
Airwallex 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.
Airwallex 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.