Clear GitHub Actions Caches from Telegram Announcements
You announce a deployment in your Telegram channel and include 'clear cache'. Notis immediately clears all Actions caches, ensuring a completely fresh run.
Trigger
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
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
Stale caches cause mysterious CI failures. Neurodivergent founders need a simple way to force-refresh builds without remembering GitHub's cache UI.
- Clear caches from Telegram without navigating GitHub UI
- Force fresh builds when debugging cache-related issues
- Reduces time spent troubleshooting stale-cache problems
- Works great for deployment announcements that need a clean slate
Setup
Build it in a few focused steps.
- 1Connect Telegram and GitHub to Notis.
- 2Create an automation with the prompt: 'When I post an announcement in the Telegram channel that includes the word clear-cache, remove all GitHub Actions caches for our repository.'
- 3Select Telegram (New Channel Post) as the trigger.
- 4Test by posting 'Deploying v1.2.0 clear-cache' and verify caches are deleted in GitHub settings.
Questions about this workflow
Can I clear caches for a specific branch only?
Yes—mention the branch name in your post: 'clear-cache for main' and Notis will clear only main's caches.
What if I include clear-cache by accident?
Notis will ask for confirmation in Telegram before clearing to prevent accidental wipes.
How long until the cache rebuilds?
On the next workflow run, Actions will recreate the cache from scratch, which typically takes longer than a cache hit.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to GitHub. A trigger fires from one place; an action lands in another.
Telegram triggers
GitHub actions
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
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.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
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 Telegram and GitHub. Any combination from 985+ 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.