Keep Code Progress Synced with Revenue Events
Stop context-switching between Stripe and GitHub to manually update issue status. Each completed checkout automatically tags issues that generated that revenue, keeping your development pipeline synced with real payments.
Trigger
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
You close a feature sale but forget to update the GitHub milestone; work status diverges from revenue reality, and you lose track of which code pays the bills.
- Issues linked to paying customers are visibly flagged with one query
- Revenue events stay connected to engineering work without manual mapping
- Clear record of which features are actually monetized
- Reduces the cognitive load of context-switching between financial and technical systems
Setup
Build it in a few focused steps.
- 1Connect Stripe and GitHub to Notis in your portal.
- 2Create an automation: 'When a checkout completes, add label revenue-verified to issues tagged #feature-[product-name]'.
- 3Set your notification channel to Slack so your team sees each revenue event in real-time.
- 4Test by completing a test checkout in Stripe and confirm the label appears on the relevant GitHub issue.
Questions about this workflow
How does Notis know which issues to label?
You define the connection in your automation prompt. For example: 'label issues that mention this customer's product' or 'label issues with milestone Spring-2025'.
Can I use multiple labels for different payment types?
Yes—tell Notis your rules: 'add label paying-customer to issues for annual plans, trial-customer for free trials'. Notis learns and applies these automatically.
What if the same checkout funds multiple features?
Notis will label all matched issues. If you want selective labeling, you can refine: 'only label issues if the checkout amount exceeds $500'.
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 985+ 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.