Check Stripe for an Existing Customer Before the Handoff
Catch existing customer records early, so the team can avoid duplicate billing profiles and start with the right context.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
A new sales lead may already have a Stripe record, but checking manually adds another interruption to the handoff.
- Check Stripe using an email included in the lead payload.
- Give the team a focused match result before billing setup.
- Reduce avoidable duplicate customer records.
Setup
Build it in a few focused steps.
- 1Connect BlitzAPI and Stripe once in Notis.
- 2Create an automation from any channel or in Automations, New Automation.
- 3In one instruction, ask Notis to list Stripe customers matching the lead email and report likely matches for human review.
- 4Choose the webhook trigger and where run reports should go.
- 5Send one real lead with a known email as a test and check the report.
Questions about this workflow
Does this workflow create a customer if it finds none?
No. This workflow checks for matches and reports the result. Use a separate approved handoff to create a Stripe customer.
What if the lead has no email?
Have Notis report that no email was supplied and request a manual review rather than treating the search as conclusive.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blitz API to Stripe. A trigger fires from one place; an action lands in another.
Blitz API 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.
Blitz API 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.