Keep Stripe customer contact details current
When a customer submits corrected contact details, let Addressfinder check them and Notis update the specified Stripe record.
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
Corrected contact details can sit in a form or support thread while Stripe still holds the old information.
- Apply customer-submitted corrections after checking them.
- Reduce copying between forms, messages, and Stripe.
- Leave a run report when details need human review.
Setup
Build it in a few focused steps.
- 1Connect Addressfinder and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and add a name and prompt.
- 3In one instruction, tell Notis to validate the submitted details and update the Stripe customer identified in the request only when suitable.
- 4Choose the webhook trigger and choose where run reports should go.
- 5Test with one real request that includes a Stripe customer ID and corrected details.
Questions about this workflow
What does the request need to include?
Include the Stripe customer ID and the contact details to check. Addressfinder can validate the submitted email or phone details.
Will unspecified customer fields be changed?
The Stripe update action changes only details provided to it. Ask Notis to update only the checked details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addressfinder to Stripe. A trigger fires from one place; an action lands in another.
Addressfinder 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.
Addressfinder 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.