Search Stripe for customers tied to a Clay account
Check whether a company in your Clay research already connects to a Stripe customer record.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Search Stripe customers
Retrieves a list of stripe customers matching a search query that adheres to stripe's search query language.
Why this helps
Without a quick account check, founders can duplicate billing conversations or overlook an existing relationship.
- Search customer records using Stripe's search query language.
- Bring possible existing customer matches into account research.
- Keep the final match decision reviewable.
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 searching Stripe customers with a supported search query derived from the Clay account request.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real account query and review the matching customers.
Questions about this workflow
Can I send any text as the search query?
The query must follow Stripe's customer search query language. Use a supported query based on the details available from Clay.
Does a match prove the records belong to the same company?
No. Search results are candidates to review. Check the returned customer details before treating a result as a confirmed match.
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.