Keep Stripe customer location details current
Send an address correction once and let Notis check it before updating the existing Stripe customer.
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
Address corrections can be lost between support conversations and the Stripe customer record.
- Validate corrections before they reach Stripe.
- Keep support updates connected to the relevant customer record.
- Avoid manually switching between address tools and Stripe.
Setup
Build it in a few focused steps.
- 1Connect Big data cloud and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis to validate the webhook address and update the identified Stripe customer with the supplied corrected details.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real customer address correction.
Questions about this workflow
How does Notis know which customer to update?
Include the Stripe customer ID in the webhook data so Notis can identify the existing record.
Does the workflow change details that were not supplied?
The Stripe update action changes only the details provided. Include the specific corrected address information in the webhook.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Big data cloud to Stripe. A trigger fires from one place; an action lands in another.
Big data cloud 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.
Big data cloud 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.