Organize Runners by Product Lifecycle
Each time you launch a new product in Stripe, GitHub self-hosted runners are automatically labeled to match—keeping your CI/CD infrastructure organized, discoverable, and aligned with your product catalog without any manual tagging work.
Trigger
Product Created Trigger
Triggered when a product is created in Stripe
Action
Add runner labels
Adds and appends custom labels to a self-hosted repository runner, which must be registered and active.
Why this helps
Products launch in Stripe, but your CI/CD runner labels don't change; workflows use outdated or incorrect runner labels, builds fail, you manually untangle the mess.
- Runners are automatically labeled to match your product catalog
- Workflows can find the right runners without manual label hunting
- CI/CD infrastructure stays organized as products grow
- Reduces cognitive load: you don't track runner-to-product mappings manually
Setup
Build it in a few focused steps.
- 1Connect Stripe and GitHub to Notis.
- 2Create an automation: 'When a product is created in Stripe, add label [product-name] to self-hosted runners in the organization'.
- 3Tell Notis how to derive labels from product data: 'use the product slug as the label, plus add label release-critical if tier is Enterprise'.
- 4Set Slack notifications and test by creating a product in Stripe sandbox; confirm the runners have the new label in GitHub.
Questions about this workflow
Can I add multiple labels per product?
Yes. Tell Notis: 'add label [product-name], plus label tier-[customer-tier], plus label region-[region]'. Notis adds all labels.
What if I want to label specific runners differently?
Tell Notis your rule: 'add [product-name] to Linux runners, add [product-name]-windows to Windows runners'. Notis filters by runner type.
Can I remove labels when a product is archived?
Tell Notis to watch for product deletion: 'when product is deleted, remove [product-name] label from all runners'. Notis will clean up automatically.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to GitHub. A trigger fires from one place; an action lands in another.
Stripe triggers
GitHub actions
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
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.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Product Created Trigger
Triggered when a product is created in Stripe
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.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
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.
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
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 Stripe 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.