Keep Stripe customer records current from verified call details
Capture clear customer detail changes from calls and apply them to the right Stripe record with a report of the update.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Customer
Updates an existing stripe customer, identified by customer id, with only the provided details; unspecified fields remain unchanged.
Why this helps
Customer changes mentioned during calls can be forgotten or entered into the wrong billing record.
- Reduce manual re-entry after customer calls
- Use a customer ID supplied in the request to target the right record
- Avoid guessing when a detail or customer identity is unclear
Setup
Build it in a few focused steps.
- 1Connect AssemblyAI and Stripe once in the Notis portal.
- 2Create an automation and name it for customer record updates.
- 3In one instruction, ask Notis to update only clearly confirmed customer details for the Stripe customer identified in the request, and report unclear or missing information.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real transcript and verify the intended customer record in Stripe.
Questions about this workflow
What information should the webhook request include?
Include the transcript and the Stripe customer ID. Notis should use only details the customer clearly confirms and report when the requested change is ambiguous.
Can this workflow create a new customer?
No. This workflow updates an existing Stripe customer using the customer ID provided in the request.
Does AssemblyAI send a customer update event?
No AssemblyAI trigger events are available here. A Notis webhook starts the workflow when a request is sent with the transcript and customer ID.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link AssemblyAI to Stripe. A trigger fires from one place; an action lands in another.
AssemblyAI 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.
AssemblyAI 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.