Block Deployments When Subscriptions End
The moment a subscription ends, any in-progress GitHub Pages deployments are automatically canceled—ensuring unpaid customers' sites don't go live, protecting your hosting resources and revenue.
Trigger
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Action
Cancel a GitHub Pages deployment
Cancels an existing, ongoing or queued github pages deployment for a repository using its `pages deployment id`.
Why this helps
A customer cancels their subscription, but their site keeps deploying and publishing; hosting costs accrue for an unpaid customer, you later discover and scramble to clean up.
- Unpaid customer sites don't go live—no wasted hosting resources
- Deployment lifecycle is automatically tied to subscription status
- Clear enforcement of revenue-based access without manual intervention
- Reduces cognitive load of tracking which customers should and shouldn't deploy
Setup
Build it in a few focused steps.
- 1Connect Stripe and GitHub to Notis.
- 2Create an automation: 'When a subscription is deleted for customer [customer-id], cancel GitHub Pages deployments for site [github-pages-site]'.
- 3Tell Notis how to identify the Pages site: 'cancel deployments for repository [repo-name]'.
- 4Set Slack notifications and test by canceling a subscription in Stripe; confirm the Pages deployment is canceled in GitHub.
Questions about this workflow
Will this remove the published site or just cancel new deployments?
Only new deployments are canceled. The published site remains until you manually remove it. If you want to unpublish, create a separate automation.
What if the customer re-subscribes quickly?
Tell Notis: 'if subscription is re-added within 7 days, restart the deployment'. Notis can auto-retry if the customer renews.
Can I give a grace period before canceling?
Yes. Tell Notis: 'wait 3 days after subscription ends, then cancel'. Notis enforces the delay before canceling.
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.