Reset custom runner labels during scheduled maintenance
Add a deliberate runner-label reset to your recurring billing maintenance checklist and get a Notis run report.
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 leave maintenance work dependent on memory and manual cleanup.
- Make runner cleanup part of a recurring routine.
- Remove all custom organization runner labels in one action.
- Keep default runner labels intact.
Setup
Build it in a few focused steps.
- 1Connect Billsby and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis to create it from any channel.
- 3Describe which organization runner should have its custom labels cleared during the maintenance routine.
- 4Choose a Notis cron schedule and where run reports should go.
- 5Test with one real runner and confirm the result in the run report.
Questions about this workflow
Will the reset remove default runner labels?
No. The action removes custom labels while default labels such as self-hosted, linux, and x64 remain.
Can a Billsby event start this workflow?
Billsby exposes no trigger events here, so use a Notis cron schedule to start the maintenance automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Billsby to GitHub. A trigger fires from one place; an action lands in another.
Billsby 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.
Billsby 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.