Automatically Add New Agents to GitHub Runner Pool
New CI/CD agents should be productively running workflows immediately. When an agent is created in Hubspot, Notis adds them to your runner pool with appropriate labels.
Trigger
Contact Created Trigger
Contact Created Trigger
Action
Add runner labels
Adds and appends custom labels to a self-hosted repository runner, which must be registered and active.
Why this helps
New agents sit unused because no one registers them with GitHub runners. Manual registration is tedious and often delayed.
- New agents are immediately active in your runner pool
- No manual runner registration or labeling required
- CI/CD workflows can use new agents without delays
- Keeps agent and runner status synchronized
Setup
Build it in a few focused steps.
- 1Connect Hubspot and GitHub to Notis.
- 2Ask Notis: 'When a new agent is created in Hubspot, add them to the GitHub runner pool with labels [label1], [label2].'
- 3Set Contact Created as your trigger.
- 4Choose your notification channel.
- 5Test by creating an agent in Hubspot and verifying they appear in GitHub runner settings.
Questions about this workflow
What labels should I use?
Common labels are 'linux', 'macos', 'windows' for OS, and 'production', 'staging' for environment. Choose based on agent capabilities.
Do agents need to be registered manually with GitHub first?
Yes, the agent software must be installed and registered. Notis adds the final labels and configuration once the agent is connected.
Can I assign agents to specific workflows?
Yes, use labels to route workflows. For example, label high-performance agents 'fast-runner' and use that label in workflows needing speed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Hubspot to GitHub. A trigger fires from one place; an action lands in another.
Hubspot triggers
GitHub actions
Contact Created Trigger
Contact Created Trigger
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
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 Hubspot and GitHub. Any combination from 1,000+ 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.