Stop Deployments When Payments Fail
The moment a charge fails, any related GitHub workflow runs are automatically canceled—stopping deployments for unpaid customers, reducing wasted CI/CD resources, and keeping your infrastructure aligned with actual revenue.
Trigger
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Action
Cancel a workflow run
Cancels a workflow run in a github repository if it is in a cancellable state (e.g., 'in progress' or 'queued').
Why this helps
A charge fails, but a workflow keeps running and deploys code for a customer who didn't pay; resources wasted, security risk if unpaid access persists, you later find out and scramble to clean up.
- Deployments stop instantly when payments fail—no wasted CI/CD cycles
- Unpaid customers don't get access to resources
- Clear link between payment status and code deployment
- Reduces infrastructure costs and cognitive overhead of manual cancellations
Setup
Build it in a few focused steps.
- 1Connect Stripe and GitHub to Notis.
- 2Create an automation: 'When a charge fails for customer [customer-id], cancel any workflow runs in progress for repository [repo-name]'.
- 3Tell Notis how to identify which workflows to cancel: 'cancel workflows with label customer:[customer-id]' or 'cancel deployments'.
- 4Set Slack notifications so you see each cancellation; test with a failed charge in Stripe sandbox.
Questions about this workflow
Will this stop builds for the customer only or all builds?
You choose. Tell Notis: 'cancel only customer-specific workflows' or 'cancel all in-progress workflows'. Notis respects your rule.
What if I want to let the workflow finish before canceling?
Tell Notis: 'wait 5 minutes then cancel'. Notis will give the workflow a grace period.
Can I restart the workflow if the payment is retried?
Yes. Create a companion automation: 'when charge succeeds, restart workflows'. Notis can retry based on your rules.
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.