Secure Repos Without Manual User Management
Don't manually chase users who owe money. After a payment intent fails, automatically block them from your GitHub repos, ensuring only paying users retain access without requiring you to babysit account management.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Block a user
Blocks an existing individual github user (not an organization or your own account), preventing them from interacting with your account and repositories.
Why this helps
A customer's payment fails; you debate whether to revoke access, manually check history, worry about losing revenue—the decision limbo costs mental energy and security lapses.
- Unpaid users are automatically blocked—no manual decisions needed
- Revenue protection without friction or ambiguity
- Reduced cognitive load: clear, rule-based enforcement happens automatically
- Audit trail of blocked accounts linked to payment failures
Setup
Build it in a few focused steps.
- 1Connect Stripe and GitHub integrations to Notis.
- 2Create an automation: 'When a payment intent fails for the second time in 30 days, block that user from my GitHub organization'.
- 3Choose Slack to receive notifications of blocked users.
- 4Test with a test payment failure in Stripe and confirm the user is blocked in GitHub.
Questions about this workflow
Can I unblock users automatically after they pay?
Yes. Tell Notis: 'when payment succeeds, unblock the user'. Notis will restore access automatically once revenue clears.
What if I want to send a warning before blocking?
You can set a multi-step rule: 'after 1st failure, send email; after 2nd failure, block'. Notis will notify and escalate in stages.
Will this affect paying users by accident?
No. Notis only acts on payment failure events. Paying users are never blocked unless their payment explicitly fails.
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.