Update a Stripe subscription after a Bolna call
When a customer confirms a subscription change, have Notis apply the specified update and report the result.
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 change requests can stall while call notes are translated into billing updates.
- Carry an authorized change into Stripe
- Reduce manual handoff from support to billing
- Report when the subscription or change details are unclear
Setup
Build it in a few focused steps.
- 1Connect Bolna and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the subscription update.
- 3In one instruction, tell Notis which authorized changes it may apply and how to handle unclear requests.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real example and verify the subscription update in Stripe.
Questions about this workflow
Can this workflow make any subscription change a caller asks for?
Define the authorized changes in the instruction and require clear confirmation. Notis should report requests outside that scope.
What if a change refers to an invalid price or other record?
Stripe requires referenced entity ids to be valid. The report should surface an unsuccessful update for follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bolna to Stripe. A trigger fires from one place; an action lands in another.
Bolna 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.
Bolna 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.