Keep Stripe customer emails current and checked
When someone submits a new email, validate it first and update the Stripe customer only if it passes.
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
A mistyped replacement email can make a customer record less useful than the old one.
- Check replacement addresses before updating a record.
- Avoid overwriting a customer email with an invalid value.
- Review each outcome in the chosen report channel.
Setup
Build it in a few focused steps.
- 1Connect Abstract and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Describe in one instruction how to validate the replacement email and update the specified customer only if it passes.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real customer example and a replacement email.
Questions about this workflow
What information should the request include?
Include the replacement email and enough information to identify the Stripe customer, such as the customer ID.
Will it update the email if validation fails?
The instruction should explicitly require a passing Abstract validation result before updating the customer.
Does it replace other customer details?
The selected Stripe action updates only the provided details; the instruction should request only the email change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abstract to Stripe. A trigger fires from one place; an action lands in another.
Abstract 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.
Abstract 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.