Verify a new phone number before saving it to Stripe
Check submitted phone changes first, then update the Stripe customer record when verification succeeds.
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
Unverified changes can leave customer records with phone numbers that are difficult to use.
- Verify replacement numbers before saving them.
- Keep existing customer details when a check does not pass.
- Make phone change outcomes easier to review.
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 verify the replacement phone number 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 number.
Questions about this workflow
How does the workflow know which customer to update?
Include the Stripe customer ID in the webhook request and tell Notis to use that customer.
What happens when verification does not pass?
Tell Notis to skip the update and include the verification outcome in its run report.
Can other customer fields change?
Instruct Notis to update only the phone number so unrelated details remain untouched.
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.