Verify phone numbers before adding Stripe customers
Give every phone number a quick verification check before it enters your Stripe customer list.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Why this helps
Unverified phone numbers make customer records harder to trust and use for follow-up.
- Catch phone number issues during customer intake.
- Create customer records only after the requested check passes.
- Reduce manual review of new customer details.
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 submitted phone number and create a customer when it passes.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real example, including a number that should fail verification.
Questions about this workflow
What does the workflow check?
It asks Abstract to verify the phone number included in the incoming webhook request.
What if the number cannot be verified?
Instruct Notis to report the result and skip customer creation when verification does not pass.
Can I test it before relying on it?
Yes. Use one real example and review the run report.
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.