Update Stripe customer details after a signed change
Carry approved customer detail changes from the signed document into Stripe.
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 updates stated in signed documents can be missed when they require a separate record edit.
- Reduce missed customer record updates
- Apply only changes explicitly supplied in the request
- Report missing customer identifiers for follow-up
Setup
Build it in a few focused steps.
- 1Connect BoldSign and Stripe once in Notis.
- 2Create an automation and describe updating only the Stripe customer details explicitly changed in the signed agreement.
- 3Pick a Notis webhook trigger and choose where run reports go.
- 4Send the Stripe customer ID and approved changes to the webhook after signature.
- 5Test with one real agreement and verify the updated customer.
Questions about this workflow
Will this replace all existing Stripe customer details?
No. The action updates only the details provided; unspecified fields remain unchanged.
What if the Stripe customer ID is missing?
Have the automation report the missing identifier for review rather than selecting a customer by guess.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Boldsign to Stripe. A trigger fires from one place; an action lands in another.
Boldsign 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.
Boldsign 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.