Review BTCPay store settings when a subscription starts
Put the store configuration in view when recurring revenue begins, so payment operations context is easy to find.
Trigger
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Action
Get Store
Tool to retrieve information about a specific store. use when you need full store configuration.
Why this helps
New recurring billing can add operational follow-up, while store settings live in a separate payment system.
- Prompt a store configuration review when recurring billing starts.
- Reduce context switching across billing systems.
- Make relevant store settings available alongside the subscription event.
Setup
Build it in a few focused steps.
- 1Connect Stripe and BTCPay Server once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel what outcome you want.
- 3In one instruction, ask Notis to retrieve and summarize configuration for the specified BTCPay Server store when Stripe adds a subscription.
- 4Choose the Stripe Subscription Added trigger and select where run reports should go.
- 5Test with one real subscription addition and review the run report.
Questions about this workflow
Will this change store settings based on the subscription?
No. It retrieves the store configuration for review and does not modify it.
Does a subscription event identify the BTCPay store?
Not necessarily. Supply the store id or a clear lookup rule in your instruction if that relationship is not provided by the event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Btcpay server. A trigger fires from one place; an action lands in another.
Stripe triggers
Btcpay server actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Payment Request
Tool to create a new payment request for a store. use after confirming store id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Store
Tool to create a new store in btcpay server. use when you need to provision a new store before processing transactions.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Create BTCPay Server User
Tool to create a new btcpay server user. use when you need to register a new user programmatically as an administrator.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Register a Webhook
Tool to register a new webhook. use when you need to receive store event notifications.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Delete API Key
Tool to revoke a specific api key. use when you need to remove an api key to immediately prevent its use. call after identifying the key to revoke.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Delete Payment Request
Tool to delete a specific payment request. use when you need to archive/remove an existing payment request for a store.
Product Created Trigger
Triggered when a product is created in Stripe
Delete Store Payout
Tool to delete a specific payout from a store. use when you need to cancel a payout no longer needed.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Get API Key
Tool to retrieve the current api key. use after authentication to get api key details.
Connect any two apps with Notis in the middle.
Stripe and Btcpay server, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Btcpay server.