Clear the cache key blocking audio pipeline work
A pipeline report names the problematic cache key, and Notis clears that cache from the specified GitHub repository.
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
A stale cache can waste time when the team has to locate and remove it by hand.
- Act on a cache key identified in the report
- Reduce manual GitHub cache cleanup
- Keep the cleanup request connected to pipeline context
Setup
Build it in a few focused steps.
- 1Connect CAMB.AI and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for cache cleanup.
- 3In one instruction, tell Notis to delete only the cache key and optional Git ref supplied in a CAMB.AI-related pipeline report.
- 4Choose the notis_webhook trigger and send the repository and cache details to it.
- 5Choose a report channel, then test with one known safe cache key.
Questions about this workflow
Does the action fail if the cache key is missing?
The GitHub action succeeds even when no matching caches are found.
Can the workflow identify corrupted cache keys by itself?
Only use a key explicitly identified in the request or in data Notis can analyze. Provide your criteria for stale or corrupted caches.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CAMB.AI to GitHub. A trigger fires from one place; an action lands in another.
CAMB.AI 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.
CAMB.AI 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.