Review Stripe customer records for account support
Have Notis list Stripe customer records using details from a new support ticket, then report what needs follow-up.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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
Looking through customer records by hand adds avoidable work when support already has useful account details.
- Use ticket details to narrow customer searches
- Reduce manual lookup steps
- Make customer record follow-up easier
Setup
Build it in a few focused steps.
- 1Connect Zendesk and Stripe once in the Notis portal.
- 2Create an automation with an instruction to list relevant Stripe customers using ticket details such as email where available.
- 3Pick the New Zendesk Ticket trigger for the account support view.
- 4Choose a report channel and test with one real account ticket.
Questions about this workflow
Can the action filter by email?
Yes. List customers supports filtering by email, creation date, or test clock, plus pagination.
Is this the same as a precise customer search?
This action lists customers with filters. For search query syntax, use the separate Search Stripe customers action.
What if multiple records match?
Ask Notis to present the matching records clearly and flag the need for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Stripe. A trigger fires from one place; an action lands in another.
Zendesk 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.
New User Created
Triggered when a new user is created in Zendesk.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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.
Zendesk 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.