Keep feedback experiments moving with clean caches
Small bits of technical housekeeping should not interrupt a founder's thinking.
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
Stale or corrupted caches make experiments slower and create avoidable debugging work.
- Reduces cache-related interruptions
- Keeps experiment repositories healthier
- Turns maintenance into a predictable background task
Setup
Build it in a few focused steps.
- 1Connect Delighted and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: Clear GitHub Actions caches matching the keys or refs used by completed Delighted feedback experiments, and report what was removed.
- 4Choose a recurring schedule, select a run-report channel, and test with one real cache key.
Questions about this workflow
Will every cache be deleted?
No. The instruction can restrict cleanup to named keys, refs, repositories, or completed experiments.
Can the workflow run weekly?
Yes. Choose a recurring schedule that matches your maintenance needs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Delighted to GitHub. A trigger fires from one place; an action lands in another.
Delighted 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 Delighted 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.