Skip to content
Notis

Bring Stripe customer context into a Clay review

See whether an enriched prospect already has a Stripe customer record before deciding what to do next.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Retrieve customer

Retrieves detailed information for an existing stripe customer using their unique customer id.

Why this helps

Prospect research and billing history can sit in separate tools, making duplicate outreach more likely.

  • Retrieve the details of an identified Stripe customer.
  • Give a prospect review relevant billing context in one run.
  • Help avoid acting on an incomplete customer picture.

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 retrieving the Stripe customer using the customer ID supplied with the Clay review request.
  • 4Choose the webhook trigger and select where run reports should go.
  • 5Test with one real customer ID and review the returned details.

Questions about this workflow

Can this search Stripe by a person's name?

This action retrieves a customer by unique Stripe customer ID. Use a separate customer search workflow if you need a search query.

Does the action change customer data?

No. Retrieving a customer returns its details without updating the record.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Confirm payment intent

Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.

ActionInstant

Create Customer

Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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`.

ActionInstant

Create product

Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.

ActionInstant

Create Refund

Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.

ActionInstant

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.