Reset stale GitHub build state from Botpress
When Botpress diagnostics point to a stale dependency or build cache, Notis clears the matching GitHub Actions cache so the next run starts clean.
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
Cache-related bot deployment failures are frustrating to recognize and easy to postpone because fixing them means leaving the diagnostic conversation for GitHub.
- Turns a known cache diagnosis into an immediate corrective action
- Avoids searching GitHub for the relevant cache key
- Helps the next bot build start from a predictable state
Setup
Build it in a few focused steps.
- 1Connect Botpress and GitHub in your Notis portal.
- 2Tell Notis in one prompt to clear the relevant GitHub Actions cache when the Botpress diagnostic webhook identifies stale or corrupted build state.
- 3Select an incoming webhook trigger and your preferred run-report channel.
- 4Test against a disposable cache key and confirm GitHub accepts the cleanup.
Questions about this workflow
Can the workflow target a branch-specific cache?
Yes. Your instruction can tell Notis to use the cache key and optional Git reference supplied by the diagnostic event.
What happens if no cache matches?
GitHub treats the clear request as successful even when no matching cache is found, and Notis can report that outcome in your chosen channel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botpress to GitHub. A trigger fires from one place; an action lands in another.
Botpress 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 Botpress 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.