Catch subscription cancellation requests during a scheduled review
Bring the request queue and current subscription records together so cancellation requests have a clear next step.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List subscriptions
Retrieves a list of stripe subscriptions, optionally filtered by various criteria such as customer, price, status, collection method, and date ranges, with support for pagination.
Why this helps
Cancellation requests can sit unnoticed when they live in a web queue separate from Stripe subscription records.
- Review a defined request queue on a recurring schedule.
- Compare requests with Stripe subscription status.
- Get a concise list of requests that need follow-up.
Setup
Build it in a few focused steps.
- 1Connect Browserbase MCP and Stripe once in Notis.
- 2Create an automation in Automations, New Automation, or describe the task to Notis from any channel.
- 3Specify the web queue to review and ask Notis to match requests to Stripe subscriptions and report recommended next steps without canceling them.
- 4Pick the Notis cron trigger and choose where run reports go.
- 5Test with one real request and confirm the report identifies the right subscription.
Questions about this workflow
Does this cancel subscriptions?
No. It lists matching subscriptions for review. Cancellation is a separate action and should follow your approval process.
Can the schedule detect new requests?
It can review the specified page when the cron runs. Browserbase MCP does not provide a native trigger event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserbase MCP to Stripe. A trigger fires from one place; an action lands in another.
Browserbase MCP triggers
Stripe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Browserbase MCP and Stripe, 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 Stripe.