Keep Stripe customer contacts current
A corrected recipient address or email can reach the billing record without another manual 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
Contact corrections made during outreach can be missed in the separate Stripe customer record.
- Apply only the customer details included in the request.
- Use the Stripe customer ID or a search by email to locate the record.
- Receive a report if the customer cannot be identified.
Setup
Build it in a few focused steps.
- 1Connect Amcards and Stripe once in the Notis portal.
- 2Create an automation for updating customer contact details.
- 3Tell Notis to find the Stripe customer using the supplied customer ID or email and update only the corrected details in the webhook request.
- 4Choose the webhook trigger and a report channel.
- 5Test with one real contact correction.
Questions about this workflow
What information should the webhook request include?
Include a Stripe customer ID or an email Notis can use to find the customer, plus the corrected details.
Will other Stripe customer fields be overwritten?
The update action changes only the provided details, so tell Notis to include only the corrections you want applied.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Amcards to Stripe. A trigger fires from one place; an action lands in another.
Amcards 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.
Amcards 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.