Compare Stripe customer records with Clay research
Get a regular view of which researched contacts already exist as Stripe customers.
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
Teams can repeat account research or miss an existing billing relationship when customer lists are reviewed manually.
- Review Stripe customers on a predictable schedule.
- Use available email details to compare with Clay research.
- Spot records that may need human follow-up.
Setup
Build it in a few focused steps.
- 1Connect Clay and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Describe listing Stripe customers and comparing available emails with the Clay account research you provide.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real customer list and review the comparison.
Questions about this workflow
Will this automatically find matching Clay records?
Notis can analyze returned data and Clay data you provide. It cannot compare against a Clay dataset that the workflow has not supplied.
Can the workflow update either system?
This workflow only lists Stripe customers. Review the report and specify a separate update action if you want records changed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clay to Stripe. A trigger fires from one place; an action lands in another.
Clay 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.
Clay 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.