Update Stripe customer details from a verified request
Turn a clear customer update request into a Stripe change while keeping its transaction context in the report.
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
Transferring a customer correction from a transaction follow-up into billing creates one more task to remember.
- Apply clearly requested customer detail changes in Stripe.
- Keep the source request visible in the run report.
- Avoid updates when the customer or requested change is unclear.
Setup
Build it in a few focused steps.
- 1Connect Blocknative and Stripe once in Notis.
- 2Create an automation from any channel or in Automations, New Automation.
- 3In one instruction, ask Notis to update only the explicitly requested customer fields for the stated Stripe customer ID and report ambiguity without changing data.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real, authorized customer update request and verify the Stripe record.
Questions about this workflow
Will unspecified customer fields be overwritten?
The action updates only provided details; unspecified fields remain unchanged.
What if the request does not identify the customer?
Have Notis report the missing identity and make no update.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blocknative to Stripe. A trigger fires from one place; an action lands in another.
Blocknative 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.
Blocknative 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.