Carry agreed subscription changes into Stripe
When a customer and your team agree on a subscription change, use the meeting recap and subscription ID to apply the specified update.
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 agreed in conversation can be forgotten or entered with the wrong plan details later.
- Record the agreed change while the call context is available.
- Update the identified, existing subscription.
- Avoid acting on tentative options that were discussed but not approved.
Setup
Build it in a few focused steps.
- 1Connect Avoma and Stripe to Notis once in the portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe that Notis should update only an existing subscription when the recap confirms the change and contains the needed valid Stripe identifiers.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real recap containing the subscription ID and agreed change details.
Questions about this workflow
Can this update a canceled subscription?
No. The Stripe action updates an existing, non-canceled subscription.
What if the call discussed several possible changes?
Instruct Notis to act only when the recap identifies one agreed change. If the decision or required identifiers are unclear, it should report the gap.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Avoma to Stripe. A trigger fires from one place; an action lands in another.
Avoma 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.
Avoma 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.