Check incoming signup records for existing Stripe customers
Before new customer records are created, Notis can compare signup details against customer records already in Stripe.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List customers
Retrieves a list of stripe customers, with options to filter by email, creation date, or test clock, and support for pagination.
Why this helps
Duplicate customer records add clutter and make billing history harder to interpret.
- Surface likely existing customer records before manual processing
- Reduce avoidable duplicate records
- Keep uncertain matches clear for review
Setup
Build it in a few focused steps.
- 1Connect Browserless and Stripe once in the Notis portal.
- 2Create an automation from any channel, or use Automations, New Automation in the portal.
- 3In one instruction, ask Notis to inspect selected signups and check Stripe customers by available email, reporting matches without creating records.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real signup batch and confirm how ambiguous matches appear.
Questions about this workflow
Will this prevent every duplicate?
It can surface matches using available signup and customer data. Variations in names or email addresses may require human review.
Does it create a new customer for a signup without a match?
No. This workflow is a review step. A separate decision or workflow can create a record after the check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserless to Stripe. A trigger fires from one place; an action lands in another.
Browserless 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.
Browserless 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.