Keep organization runner labels tidy on a schedule
Set a recurring cleanup for the custom labels on a self-hosted organization runner.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Clear self-hosted runner org labels
Removes all custom labels from a self-hosted runner for an organization; default labels (e.g., 'self-hosted', 'linux', 'x64') will remain.
Why this helps
Custom runner labels can accumulate and make it harder to understand how runners are categorized.
- Remove accumulated custom labels on a recurring schedule.
- Retain GitHub's default runner labels.
- Reduce periodic manual runner cleanup.
Setup
Build it in a few focused steps.
- 1Connect Apiverve and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to clear custom labels from the specified organization runner while preserving default labels.
- 4Choose a recurring schedule trigger and select where Notis should send run reports.
- 5Test with one real runner and confirm only custom labels are removed.
Questions about this workflow
Will default labels be removed?
No. The action removes custom labels and retains default labels such as self-hosted, linux, and x64.
What should the prompt identify?
Specify the organization and runner to clean up so Notis does not guess which runner to change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apiverve to GitHub. A trigger fires from one place; an action lands in another.
Apiverve 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.
Apiverve 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.