Update a Stripe subscription after an approved offer change
Carry a confirmed offer change through to the subscription record without rebuilding the billing context.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Subscription
Updates an existing, non-canceled stripe subscription by its id, ensuring all referenced entity ids (e.g., prices, coupons) are valid and automatic tax liability is correctly specified if enabled.
Why this helps
Subscription changes can be delayed when the approved commercial decision and Stripe update happen in separate work sessions.
- Keep a subscription update tied to its approved offer change.
- Use supplied valid entity identifiers for the requested change.
- Reduce the chance that a billing change remains only in a campaign note.
Setup
Build it in a few focused steps.
- 1Connect Abyssale and Stripe once in the Notis portal.
- 2Create an automation named for applying approved subscription changes.
- 3Tell Notis to update the existing non-canceled Stripe subscription using the valid changes specified in each approved request.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real approved request and review the resulting subscription in Stripe.
Questions about this workflow
Can this update a canceled subscription?
No. The listed action updates an existing subscription that is not canceled.
What should the request include?
Identify the subscription and specify the approved changes using valid Stripe entity identifiers where applicable.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abyssale to Stripe. A trigger fires from one place; an action lands in another.
Abyssale 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.
Abyssale 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.