Update recurring billing after an agreed scope change
Carry an approved change into the billing record with the relevant details in one request.
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
Agreed scope changes can leave recurring billing out of date when nobody owns the final update step.
- Bring approved recurring billing updates into the workflow.
- Use explicit subscription and change details from the request.
- Keep a report of the subscription update run.
Setup
Build it in a few focused steps.
- 1Connect Better Proposals and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Ask Notis to update the existing Stripe subscription using only the approved changes and identifiers included in the request.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one approved example and review the subscription change in Stripe.
Questions about this workflow
Can this workflow decide whether a scope change is approved?
No. The request must represent an approved change and include the intended billing update.
What does it need to identify the subscription?
Include a valid Stripe subscription ID and the details of the requested change. The action requires valid referenced IDs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Better proposals to Stripe. A trigger fires from one place; an action lands in another.
Better proposals 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.
Better proposals 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.