Automate GitHub Runner Configuration from Notion
Infrastructure specs are updated in Notion. Notis instantly labels your GitHub self-hosted runners, so CI/CD workflows find the right machines.
Trigger
Page Properties Updated
Fires when a page’s properties are updated.
Action
Add runner labels
Add custom labels to a self-hosted repository runner.
Why this helps
Runners are tagged manually but Notion has the real state of infrastructure. When specs change in Notion, runner labels get stale, causing CI failures or jobs routing to wrong machines.
- Keep runner labels in sync with actual infrastructure
- Reduce CI failures from wrong runner selection
- Automate runner setup on infrastructure changes
- Make infrastructure changes immediately effective
Setup
Build it in a few focused steps.
- 1Connect Notion and GitHub integrations.
- 2Create a Notion database for infrastructure specs (CPU, RAM, OS, etc.).
- 3Tell Notis: 'When infrastructure specs are updated in Notion, add the matching custom labels to my GitHub self-hosted runners.'
- 4Verify which runners to label.
- 5Test by updating one infrastructure entry in Notion.
Questions about this workflow
How does Notis know which runner to label?
You provide a runner name or identifier in Notion, and Notis matches it.
Can one runner have multiple labels?
Yes. Notis adds all labels corresponding to the runner's properties.
What happens to old labels?
Tell Notis to remove old labels before adding new ones, or keep both.
When this happens · Trigger
Fires when a page’s properties are updated.
Do this · Action
Add custom labels to a self-hosted repository runner.
Supported Triggers and Actions
Notis builds workflows that link Notion to GitHub. A trigger fires from one place; an action lands in another.
Notion triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accept a pending repository invitation.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Abort Repository Migration
Aborts a queued or ongoing repository migration.
Comment Created
Fires when a new comment is created in the accessible workspace.
Add email for auth user
Add email addresses to your account.
Database Created
Fires when a new database container is created.
Add app access restrictions
Allow apps to push to a protected branch.
Data Source Created
Fires when a new data source is created in the workspace.
Add a repository collaborator
Add a user as a repository collaborator or update their access.
Data Source Schema Updated
Fires when a data source’s columns are added, removed, or renamed.
Add field to user project
Adds a custom field to a user-owned project.
Page Content Updated
Fires when the body content of an accessible page is updated.
Add a repository to an app installation
Grant an app access to a repository.
Page Created
Fires when a new page is created in the accessible workspace.
Add item to user project
Adds an issue or pull request to a user-owned project.
Connect any two apps with Notis in the middle.
Notion and GitHub, or any other combination from 1,700+ 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.